1.1

On Sat, 2008-01-26 at 17:08 -0800, Zac Medico wrote:
> 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?

1. Add blocking of commit of files/digest-* in CVS pre-commit hook
2. Add manifest1_obsolete to tree
3. Remove all files/digest-* files from tree (on CVS server side)
4. Remove all files dirs that are empty (on CVS server side)

This should be all that we need.  The 2007.1 snapshot was done without
any digest files, and it worked just fine, also the default settings
have been to not sync the digest files for some time, so only people
with an older/unsupported portage have been getting digest files, at
all.

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.

-- 
Chris Gianelloni
Release Engineering Strategic Lead
Games Developer