On Sun, 2008-01-27 at 18:01 -0800, Robin H. Johnson wrote: > On Sun, Jan 27, 2008 at 05:34:14PM -0800, Chris Gianelloni wrote: > > On Sun, 2008-01-27 at 06:27 -0800, Robin H. Johnson wrote: > > > Due to how CVS hooks operate, it's not quite possible. > > > You wouldn't be able to block the entire commit, only the contents of > > > the files/ directory would get totally blocked. > > > If you were committing an ebuild along with a patch, this would be very > > > bad, as the ebuild+Manifest would get committed, but the patch wouldn't. > > Bleh... CVS vs. SVN. There's no "pre-commit" equivalent on CVS? > There is pre-commit, but it's not recursive. It gets applied to only a > single directory and in isolation from the other directories.
OK. So we could block on commits of digest-* files to files, right? What else would we need? > > Also, wouldn't the second Manifest run "fix" the missing digest commit? > In what way? the problem I was concerned about was non-digest files > not being committed leading to broken ebuilds. Ahh, never mind... I was thinking of something else. -- Chris Gianelloni Release Engineering Strategic Lead Games Developer
signature.asc
Description: This is a digitally signed message part
