Difference between pages "Package:Eix" and "Translations:Metro/122/en"

(Difference between pages)
m (I missed a few <console> tags apparently...)
 
(Importing a new version from external source)
 
Line 1: Line 1:
{{Ebuild
+
On my AMD Jaguar build server, on Feb 20, 2015, this lists all the builds that {{c|buildrepo}} has been configured to manage. The first number on each line is a '''failcount''', which is the number of consecutive times that the build has failed. A zero value indicates that everything's okay. The failcount is an important feature of the advanced repository management features. Here are a number of behaviors that are implemented based on failcount:
|Summary=A command to search and query ebuilds, portage including local settings, overlays, version changes, and more.
+
|CatPkg=app-portage/eix
+
|Maintainer=
+
}}
+
== Install ==
+
To install eix, emerge it:
+
{{console|body=
+
###i## emerge eix
+
}}
+
=== Update ===
+
To include your layman repositories for synchronization:
+
{{console|body=###i## echo "*" >> /etc/eix-sync.conf }}
+
Update eix by running:
+
{{console|body=###i## eix-update}}
+
== Use ==
+
The basic usage of eix is simply using its name as a prefix to the package you are looking for:
+
{{console|body=###i## eix foo}}
+
This will give you a fairly verbose list of packages containing the term 'foo' in their name. It gives you information about which versions are available, whether they are stable, current or live, a description of the package and a list of the USE flags '''for all the packages combined''' - sometimes different versions of packages have different USE flags so you may need to check which a specific package contains with equery.
+
=== More detailed example ===
+
Suppose that you are interested in learning about the various available kernels in Portage. Eix can help with that. By running the following command, you will find the answer that you are looking for:
+
{{console|body=
+
###i## eix -# sys-kernel/
+
}}
+
To receive more information in the output, add the {{c|-c}} argument when you run eix:
+
{{console|body=
+
###i## eix -c sys-kernel/
+
}}
+
=== Showing what you have installed ===
+
 
+
A handy feature of eix is the ability to quickly show you which packages you have installed on your system.  
+
{{console|body=###i## eix-installed all}}
+
This will output all the packages you have explicitly installed along with the version number. There are other options to get more specific information with this command so check the man page for details.
+
 
+
This can be handy for when you do backups of your system, the list could be sent to a file before you run rsync:
+
{{console|body=###i## eix-installed all > ~/installed_list.txt}}
+
=== Searching other overlays ===
+
 
+
It is possible search in more than just the main portage tree and your local overlay. By using the <b>{{c|eix-remote}}</b> command you can configure eix to load, update and search multiple external overlays.
+
 
+
To add the list of external overlays to eix:
+
{{console|body=
+
###i## eix-remote update
+
###i## eix-sync}}
+
Now you are ready to search for packages inside the main funtoo portage tree and in all the third party overlays by using the <b>{{c|-R}}</b> argument:  
+
{{console|body=###i## eix -R foo}}
+
 
+
This is will give you a list of all the packages and versions, as well as telling you which overlay they belong to. Once you have found something you want to emerge you can add the overlay, with either
+
{{console|body=###i## layman -a [overlay_name]}}
+
or by using  <b>{{c|eix-layman}}</b>, and then just emerge the package in the normal way.
+
 
+
{{EbuildFooter}}
+

Latest revision as of 17:31, July 12, 2015

On my AMD Jaguar build server, on Feb 20, 2015, this lists all the builds that buildrepo has been configured to manage. The first number on each line is a failcount, which is the number of consecutive times that the build has failed. A zero value indicates that everything's okay. The failcount is an important feature of the advanced repository management features. Here are a number of behaviors that are implemented based on failcount: