-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03.01.2012 15:47, Alan McKinnon wrote: > On Tue, 03 Jan 2012 15:05:56 +0100 Hinnerk van Bruinehsen > <h.v.bruineh...@fu-berlin.de> wrote: > >>>> Really, the proposal to 'fix --update' doesn't address >>>> really knowing what your system is running and why. Get to >>>> the root of that and the --update thing becomes the non-issue >>>> that many of us think it is. >>>> >>> >>> This would be a suggestion to travel back in time and document >>> something that I have no way of knowing now. >>> >> You could create your own overlay with "meta"-ebuilds, e. g. >> system-maintenance, customer1, customer2. Inside the ebuilds you >> define depends on the packages the customer wants. Doing so you >> could wipe everything except the "meta"-ebuilds from world. When >> a customer quits you can unmerge his or her "meta"-ebuild and >> depclean. If you add everything needed to the respective >> "meta"-ebuild, you'll always be on the safe side. > > > Sets do exactly the same thing simply without all the added > verbiage of an ebuild. > > The *only* thing required to bring about the solution you describe > is the information in the *DEPEND of the meta-ebuild, and that is > all that is in a set. >
Then I should try to find some information on sets (custom defined ones). Thank you for the hint! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPAxXjAAoJEJwwOFaNFkYcP64H/0sl77a1uFXW5hL0hM1A5fSN PzKAErLc6inDRzzs0KnsDrFgkDhmPdebga2JG99IGzk+fpS77Cdu6SQUrOvkRwlF 7uzRXXCSCPxOnaHcP6ONVekeOr2HObgc6xPg1fZ8/AK2sbBozjX3N+HTgE0Wl8fW CReSK9kLmseN0YZULD0FvpuvHHs5Rda0VnFl1huY8JJWzUUOxkEkkOcrVCKjLC0I SDO4i5UCtG/pKCUby1/r1m06tR5WuiDm/hQ8/wEMB4C7/a4tZIJ0HcJjtAMYZOvH GIEP2uUIPbhC/rWwnTeM12e0ukWkNVwEnu/dyIhVhV8JOaEJi6ADgKRgimvWJo8= =d+9f -----END PGP SIGNATURE-----
