On Wed, Jul 02, 2008 at 06:49:25PM +0200, Vincent Beffara wrote: > > Nevertheless, the general question is interesting in itself. What to do > if one wants to follow the SVN version of a package ? Can one assume > that the build machine will have network access ? (It kind of has to > if only to download the source tarball, but I can imagine scenarios > where you download lots of sources in bulk and then compile while on the > road ...) > > I am interested in something similar myself, and thought essentially of > two solutions : > > (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 ... > > (ii) ship a base tarball that is close to the SVN trunk, and make a > patch script that calls SVN to catch up with the trunk itself. Then the > .deb file depends on the compilation date, which is wrong for > distribution but useful for a local package, as "fink rebuild" will then > automate most of it. > > Solution (i) sounds acceptable, but it would be fantastic to have fields > like Repository: and Revision: in finkinfo file ! > > And solution (ii), to be implementable properly, would need to compute > the package version number from the current revision, which afaik is not > doable right now.
You could use the svn revision value as the fink package Version and then 'svn update -r %v' in PatchScript. dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------------------------- 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
