> > > > (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).
Agreed, but this is not what I meant - I mean calling svn with a specific revision number (which would of course also be part of the fink version number). Then the result _is_ guaranteed to be the same. Would that be acceptable ? /v -- Vincent Beffara UMPA - ENS-Lyon 46 allée d'Italie 69364 Lyon Cedex 07 Tél : 04 72 72 85 25 ------------------------------------------------------------------------- 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
