From: Michael R. <mr...@bl...> - 2004-02-03 23:59:35
|
Is there any reason (backwards compatibility aside) the .urls file is even in the package (as opposed to parallel to it, elsewhere in the package archive)? Mike Dave Benson writes: > hmm, that's a pretty interesting point... > > i've gotta say, i think making the .urls > mutable like this seems reasonable, except > that they happen to be included in the .md5sums > file, which i've always thought of as a fingerprint > of the package. > > since build-package-archive keeps a file cache > by md5sum, if we just sorted by releases descending it > would effectively cause later .urls files to have precedence. > > that being said, I dunno if it really makes any practical difference, > so a policy workaround isn't too distasteful, especially > since it's just stating existing practice... > > - dave > > > On Tue, Feb 03, 2004 at 02:36:34PM -0800, Heather Sherman wrote: > > > > > Personally, I've always advocated a new package for any change... > > > This isn't really a hard policy to live with, since 'cheesy-release' > > > tends to do pretty well. > > > > Well, I don't think a new release should be created if the .urls is > > updated (it sounds like you weren't excepting that one, Dave). > > > > The point of updating the .urls is to make the packagearchive build > > nicely which won't happen if the old .urls file is left around in an > > old release. This could lead to a case where the packagearchive could > > not serve certain releases out to projects if the archive ever had to > > be rebuilt from scratch. This is even less desirable than having > > unexpected packages get added to a project. > > > > I'm in the "any other change should result in a new release" camp, > > though. > > > > Heather > > > > > > > > ------------------------------------------------------- > > The SF.Net email is sponsored by EclipseCon 2004 > > Premiere Conference on Open Tools Development and Integration > > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > > http://www.eclipsecon.org/osdn > > _______________________________________________ > > Wigwam-devel mailing list > > Wig...@li... > > https://lists.sourceforge.net/lists/listinfo/wigwam-devel > > -- > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > Wigwam-devel mailing list > Wig...@li... > https://lists.sourceforge.net/lists/listinfo/wigwam-devel |