Re: [gentoo-dev] News item: World file handling changes in Portage-2.2
On Fri, 5 Sep 2008 17:24:57 +0200 Marius Mauch [EMAIL PROTECTED] wrote: - another idea that hasn't been mentioned yet is that we could simply inject @system into world_sets in the portage ebuild when we detect a 2.1-2.2 upgrade (the ebuild already does a few other migrations that way). That would be the least-invasive way to keep the old behavior, but only works for poeple who haven't upgraded to 2.2 yet (not sure if that's a pro or contra) This solution has been implemented now (to be released with 2.2_rc9). Marius -- Public Key at http://www.genone.de/info/gpg-key.pub In the beginning, there was nothing. And God said, 'Let there be Light.' And there was still nothing, but you could see a bit better. signature.asc Description: PGP signature
Re: [gentoo-dev] News item: World file handling changes in Portage-2.2
On Sat, 16 Aug 2008 22:39:41 +0300 Petteri Räty [EMAIL PROTECTED] wrote: As per glep 42 (http://www.gentoo.org/proj/en/glep/glep-0042.html) here is the required email for a new news item. This news item is important because otherwise users will be missing updates to the system set if they continue updating their system with the usual emerge --update --deep world. Unless objections come out the new news item will be committed at the same time as rc8 (rc8 will have an update man portage page describing world_sets). Title: World file handling changes in Portage-2.2 Author: Petteri Räty [EMAIL PROTECTED] Author: Zac Medico [EMAIL PROTECTED] Content-Type: text/plain Posted: 2008-XX-XX Revision: 1 News-Item-Format: 1.0 Display-If-Installed: sys-apps/portage-2.2_rc8 As of Portage 2.2 the world set does not include the system set any more. If you want emerge --update --deep @world to update the system set too, you need to add @system to the new world_sets file in /var/lib/portage/. For more information on world_sets see man portage. Sorry for not replying earlier, I was without mail access for the last few weeks. First, regarding the news item, I'd suggest that instead of telling users to modify world_sets manually to use `emerge --noreplace @system`. Also there have been more changes that might not be as obvious and only affect people with unusual usage patterns, namely `emerge @world` without using --update or --noreplace will rebuild packages contained in @world (same is true for all other sets). Second for the suggestions on how to handle the transition: - treating 'world' and '@world' differently is a no go from my POV. One of the main reasons to implement them as sets was to remove special case code in emerge, so I'm quite opposed to adding new special cases instead. And I'm quite sure that such a separation would cause confusion, and some isues regarding (end-user) documentation. - adding a new @worldfile set to get the new behavior, and use @world for the old. That one is quite interesting, and should actually be rather simple to implement: rename the existing @world to @worldfile, create a new StaticFileSet @world that just contains @worldfile and @system (stored in /usr/share/portage), change most references in emerge from @world to @worldfile (for technical reasons, the WorldSet class is somewhat special), and add world-candidate=False to the default sets.conf - issuing a warning if 'world' is the only argument would also be a special case, but by far not as invasive as the first suggestion. I've actually considered to mark 'world' and 'system' without the set prefix as deprecated but thought it would be too invasive/annoying at this time. - another idea that hasn't been mentioned yet is that we could simply inject @system into world_sets in the portage ebuild when we detect a 2.1-2.2 upgrade (the ebuild already does a few other migrations that way). That would be the least-invasive way to keep the old behavior, but only works for poeple who haven't upgraded to 2.2 yet (not sure if that's a pro or contra) Though honestly I don't think this issue is as big as some other people make it. People might miss some updates. The same would happen if we remove packages from @system, or people switch profiles (so @system changes). Marius
Re: [gentoo-dev] News item: World file handling changes in Portage-2.2
Marius Mauch wrote: First, regarding the news item, I'd suggest that instead of telling users to modify world_sets manually to use `emerge --noreplace @system`. ++ Second for the suggestions on how to handle the transition: - treating 'world' and '@world' differently is a no go from my POV. One of the main reasons to implement them as sets was to remove special case code in emerge, so I'm quite opposed to adding new special cases instead. And I'm quite sure that such a separation would cause confusion, and some isues regarding (end-user) documentation. +++ -Joe
[gentoo-dev] News item: World file handling changes in Portage-2.2
As per glep 42 (http://www.gentoo.org/proj/en/glep/glep-0042.html) here is the required email for a new news item. This news item is important because otherwise users will be missing updates to the system set if they continue updating their system with the usual emerge --update --deep world. Unless objections come out the new news item will be committed at the same time as rc8 (rc8 will have an update man portage page describing world_sets). Title: World file handling changes in Portage-2.2 Author: Petteri Räty [EMAIL PROTECTED] Author: Zac Medico [EMAIL PROTECTED] Content-Type: text/plain Posted: 2008-XX-XX Revision: 1 News-Item-Format: 1.0 Display-If-Installed: sys-apps/portage-2.2_rc8 As of Portage 2.2 the world set does not include the system set any more. If you want emerge --update --deep @world to update the system set too, you need to add @system to the new world_sets file in /var/lib/portage/. For more information on world_sets see man portage. signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] News item: World file handling changes in Portage-2.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Aug 16, 2008 at 10:39:41PM +0300, Petteri R??ty wrote: Title: World file handling changes in Portage-2.2 Author: Petteri R??ty [EMAIL PROTECTED] Author: Zac Medico [EMAIL PROTECTED] Content-Type: text/plain Posted: 2008-XX-XX Revision: 1 News-Item-Format: 1.0 Display-If-Installed: sys-apps/portage-2.2_rc8 As of Portage 2.2 the world set does not include the system set any more. If you want emerge --update --deep @world to update the system set too, you need to add @system to the new world_sets file in /var/lib/portage/. For more information on world_sets see man portage. This brings up a question. I have been doing updates this way: emerge -NDu @installed Does that do the same thing? Thanks, - -- William Hubbs gentoo accessibility team lead [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkinguMACgkQblQW9DDEZTiwZgCff3r0XtUR2iGGswpfTkWxEQcp xisAoKZDrcjbh9T1SikiaASpyqqEKq/A =e9j2 -END PGP SIGNATURE-
Re: [gentoo-dev] News item: World file handling changes in Portage-2.2
2008-08-17 03:46:11 William Hubbs napisał(a): On Sat, Aug 16, 2008 at 10:39:41PM +0300, Petteri R??ty wrote: Title: World file handling changes in Portage-2.2 Author: Petteri R??ty [EMAIL PROTECTED] Author: Zac Medico [EMAIL PROTECTED] Content-Type: text/plain Posted: 2008-XX-XX Revision: 1 News-Item-Format: 1.0 Display-If-Installed: sys-apps/portage-2.2_rc8 As of Portage 2.2 the world set does not include the system set any more. If you want emerge --update --deep @world to update the system set too, you need to add @system to the new world_sets file in /var/lib/portage/. For more information on world_sets see man portage. This brings up a question. I have been doing updates this way: emerge -NDu @installed Does that do the same thing? No. @installed set contains all installed packages. -- Arfrever Frehtes Taifersar Arahesis signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] News item: World file handling changes in Portage-2.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 William Hubbs wrote: As of Portage 2.2 the world set does not include the system set any more. If you want emerge --update --deep @world to update the system set too, you need to add @system to the new world_sets file in /var/lib/portage/. For more information on world_sets see man portage. This brings up a question. I have been doing updates this way: emerge -NDu @installed Does that do the same thing? It's mostly the same, except for things that are eligible for removal by emerge --depclean. I advise people to use @world and @system instead of @installed whenever possible since @installed makes it impossible for emerge to solve blockers by automatic uninstallation of blocked packages [1]. I've recently updated the documentation to warn about this undesirable side-effect [2]. [1] http://planet.gentoo.org/developers/zmedico/2008/05/09/blocking_package_file_collisions [2] http://sources.gentoo.org/viewcvs.py/portage?view=revrev=11318 - -- Thanks, Zac -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkinlvwACgkQ/ejvha5XGaOv3gCgvdPJY/Nl8Hoxou12Kp2bw7jQ 6r0AnjiYH/yHs3aC5W9k8KE4f1ySDtLX =p+ib -END PGP SIGNATURE-
