| 1 |
On Samstag, 31. Mai 2008, Beso wrote: |
| 2 |
another good thing of paludis is the use of sets that |
| 3 |
> include a list of packages. i've actually been using them to update live |
| 4 |
> packages without putting them all hand by hand everytime. |
| 5 |
|
| 6 |
http://www.pkgcore.org/trac/pkgcore/wiki/Features |
| 7 |
|
| 8 |
http://www.pkgcore.org/trac/pkgcore/doc/doc/getting-started.rst |
| 9 |
---> |
| 10 |
Sets |
| 11 |
Available sets are dependent upon your configuration. The majority of users |
| 12 |
still use /etc/make.conf configuration, which has five default sets: |
| 13 |
system, world, installed, version-installed, glsa |
| 14 |
system, world: |
| 15 |
These two are the same as in portage. |
| 16 |
version-installed: |
| 17 |
versioned-installed is a set of all CPVs from the vdb. This is useful |
| 18 |
for --emptytree. |
| 19 |
Example: |
| 20 |
If you have app/foo-1 and bar/dar-2 installed (and just those), |
| 21 |
versioned-installed would be a set containing -app/foo-1 and -bar/dar-2. |
| 22 |
installed: |
| 23 |
installed is an unversioned set, but is slotted. Unlike version-installed, |
| 24 |
installed can be used for "system update". Using pmerge -us installed over |
| 25 |
pmerge -u -s system -s world also has the advantage that dependency-orphaned |
| 26 |
packages are updated. |
| 27 |
Example: |
| 28 |
If you had app/foo-1 slot 1, app/foo-2 slot 2, installed would be a set |
| 29 |
containing app/foo:1 app/foo:2. |
| 30 |
glsa: |
| 31 |
Packages that are vulnerable to security bugs, as specified in their |
| 32 |
appropriate Gentoo Linux Security Advisory (GLSA). |
| 33 |
Custom Sets |
| 34 |
Doing this for a make.conf configuration is pretty simple. Just add a file |
| 35 |
to /etc/portage/sets, containing a list of atoms. The set name is the |
| 36 |
filename. |
| 37 |
Example: Making a kde set: |
| 38 |
pquery 'kde-*/*' --no-version > /etc/portage/sets/kde-set |
| 39 |
pmerge -uDs kde-set |
| 40 |
<----- |
| 41 |
|
| 42 |
----> |
| 43 |
|
| 44 |
New in pkgcore: |
| 45 |
--ignore-failures: |
| 46 |
Ignore resolution/build failures, skipping to the next step. Think of it as |
| 47 |
the equivalent of --skipfirst, just without the commandline interruption. |
| 48 |
It goes without saying that this feature should be used with care. It is |
| 49 |
primarily useful for a long chain of non-critical updates, where a failure is |
| 50 |
not an issue. |
| 51 |
A good example of usage is if you want to build mozilla-firefox and openoffice |
| 52 |
overnight: both take a long while to build (including their dependencies), |
| 53 |
and the user is after getting as many packages built for the targets as |
| 54 |
possible, rather then having the 5th build out of 80 bail out without even |
| 55 |
attempting the other 75. |
| 56 |
Long term, this feature will likely be replaced with a more finely tuned |
| 57 |
option. |
| 58 |
|
| 59 |
<----- |
| 60 |
|
| 61 |
people who asked for a similar functionality in paludis were called stupid. |
| 62 |
(asking for skipfirst equivalent) |
| 63 |
-- |
| 64 |
gentoo-amd64@l.g.o mailing list |
Archives