Skip to main content

arhclinux list aur packages

List AUR installed packages

yaourt -Qm 

local/chromium-pepper-flash 1:
local/firefox-nightly 41.0a1.20150526-1
local/freshplayerplugin 0.2.4-1
local/gdk-pixbuf 0.22.0-12
local/glib 1.2.10-12
local/gnome-colors-icon-theme 5.5.1-2
local/gnome-colors-icon-theme-extras 5.5.1-2
local/gnome-themes-extras 2.22.0-3
local/google-chrome 43.0.2357.81-1
local/gtk 1.2.10-15
local/gtk-theme-numix-ocean 2.0.2-2
local/hal 0.5.14-22
local/hal-info 0.20091130-2
local/itcl3 3.4.1-1
local/libpurple-meanwhile 2.10.11-1
local/libxfcegui4 4.10.0-5
local/meanwhile 1.0.2-8
local/package-query 1.5-2
local/pdsh 2.29-2
local/prips 0.9.9-1
local/tcptraceroute 1.5beta7-8
local/thunar-shares-plugin 0.2.0.git-2
local/ttf-office-2007-fonts 1.0-2
local/ttf-win7-fonts 7.1-8
local/ubuntu-font-family-console 0.80-0
local/vmware-systemd-services 0.1-2 (vmware)
local/xfce-theme-murrine-unity 20110416-4
local/xfce4-quicklauncher-plugin 1.9.4-10 (xfce4-goodies)
local/yaourt 1.5-1 


Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href=''" parameter. npm run build --base-href=' did not set the base href in indext.html After looking for a while, I found where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='

dockerfile multiline to file

Outputing a multiline string from Dockerfile I motsly use a Dockerfile by sourcing from a base ditribution: CentOS or Debian. But I also have a local mirror and would like to use it for packages installation. Espacially on CentOS it is about many lines to write to the /etc/yum.repos.d/CentOS-Base.repo file. Easiest way: one RUN per line The first method that comes in mind is to issue one RUN per line to write. Here you are: RUN echo "[base] " > /etc/yum.repos.d/CentOS-Base.repo RUN echo "name=CentOS-$releasever - Base " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "baseurl= " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "gpgcheck=0 &quo

Jira workflow for new projects

Associated workflow creation I'm a Jira Cloud user and begining from some version 6, I noticed that when I create a project, it automatically creates a Workflow and Issue Scheme that is prepended by the project key and which is a copy of the default scheme. I always had to make a cleanup after creating a project. Default workflow for new projects I also miss a feature that would allow me to make a custom workflow (and globally custom project setting) the default for new projects I create. Solution: Create with shared configuration While searching, I noticed that with Jira Cloud which is version 7.1.0 at the time I write, there is a link at the bottom of the "Create project" wizard: "Create with shared configuration" will allow me to select the project I want the new one to share configuration with. The new created project will use the same configuration as the project I select There will be no creation of Workflow and Issue Scheme that