On Thu, Oct 8, 2009 at 4:14 PM, Ben Walton <[email protected]> wrote: > Excerpts from Maciej (Matchek) Blizinski's message of Thu Oct 08 11:08:23 > -0400 2009: > >> I thought the same way, but there was a thread on this list (I >> couldn't find it in the archives) in which somebody said that the >> package file should be removed from testing when it's being send to >> the release manager. Intuitively, I would think that it's best if the >> files stays in testing/ until it's released, to avoid a gap in the >> file availability. > > The tool that pushes files to the mirrors and registers it in the DB > should also reach in an rm the file iff the filename and md5sum match. > That gets the best of both worlds. The release script is then simply > a wrapper around an email (or other trigger) to the release system.
Yes, primarily it would be a wrapper around e-mail. I also thought about making it move files around a little. For instance, copy files from testing/ to newpkgs/ and store state, or log the activity for future reference. (When did I send this? What were the checksums? etc.) Maciej _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers
