On Thursday 03 July 2008 09:36:20 Vincent Beffara wrote: > > > (i) ship a base tarball that is close to the SVN trunk, and make a > > > patch script that calls SVN to catch up to a prescribed revision > > > number. The base tarball might be empty but it's not nice to the server > > > ... > > > > An acceptable method (that has been used by some packages) is to get the > > diff to an svn or cvs version and make a patch file from it. > > Sure, that's doable, but it becomes quite tedious if you want to track a > fast-moving project ... Are you implying that it is _not_ acceptable to > call svn (or cvs or git or whatever) from the patch script ? > > /v
That violates a central paradigm of Fink: a package description should produce identical build results on different machines (as much as possible). Calling cvs/svn/git from the patch script means that a package with the same version and revision could quite possibly not be be the same on two identical machines if one of them built the package after a change in the upstream repository; and there's no way for dpkg to differentiate which is newer. ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Fink-devel mailing list [email protected] http://news.gmane.org/gmane.os.apple.fink.devel
