-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Now that the whole tree has been converted to Manifest2 format we can remove the old digest files from the tree so that it is pure Manifest2 format [1]. Any users who still have a version of portage that doesn't support Manifest2 (less than sys-apps/portage-2.1 or stages prior to 2006.1) will still be able to use a script to generate the old digests if they want to upgrade an old system [2].
In order to trigger removal of the old digests, all that we have to do is add a file named manifest1_obsolete to the root of the repository. Presence of that file causes repoman to automatically remove the old digests upon commit. If people don't update their whole cvs tree then they are likely to miss this file which will cause them to generate the old digest files and add them back to the tree unnecessarily. If that happens then it's not a major problem but we should try to make sure that everybody gets the file in order to prevent confusion. After we've added the manifest1_obsolete file we can either let the old digest files disappear gradually or we can actively remove them. It's possible to use repoman to remove them from a single package, from a whole category, or from the whole tree at once. The repoman --force option can be used to make it work faster by skipping dependency checks. If we want to actively remove them then the best approach is probably to use repoman to remove them from one category at a time. If there are no objections then I don't so any reason not to go ahead and add the manifest1_obsolete sometime in the near future. Thoughts? Zac [1] http://www.gentoo.org/proj/en/glep/glep-0044.html#removal-of-digest-files [2] http://www.gentoo.org/proj/en/portage/doc/converting-manifest2.xml -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) iD8DBQFHm9mY/ejvha5XGaMRAgFYAKCKKTZjYbLl1E/Djj/5VQp2jMzT9QCeK6N/ Ze0SmeWEhOsF4J3avthW/TQ= =/HZV -----END PGP SIGNATURE----- -- gentoo-dev@lists.gentoo.org mailing list
