-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Gianelloni wrote: > I do have one question, though. What does an older portage version do > when it hits a package with a missing digest file? > > Let's say I've got portage prior to 2007.0's, so it doesn't support > Manifest2 only. I want to "emerge --oneshot portage" to get to the > latest version. What do I need a digest on? Just portage? portage and > its dependencies? Which dependencies? All of them, or just the ones > I'll actually need to merge? > > I guess what I'm asking is if it is possible to have repoman create a > digest for sys-apps/portage only, for the slow upgraders. Of course, > this assumes its even possible on the portage side to bother. If not, > just ignore this part. >
All that they have to do is run the manifest221 script [1] and it will generate the old style digest files containing SHA1 digests from the Manifest files. I've tested that script on a 2005.0 stage3 and I was able to upgrade it pretty smoothly. [1] http://www.gentoo.org/proj/en/portage/doc/converting-manifest2.xml -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) iD8DBQFHnUIw/ejvha5XGaMRAi1XAJ9JE0aE9MwuSF+XRBi4SrMwFtkpxQCgpC2Z WEHpxtkRaquXWwLV34Nv8LI= =o11+ -----END PGP SIGNATURE----- -- gentoo-dev@lists.gentoo.org mailing list
