On Thu, Apr 15, 2010 at 4:15 PM, Jack Howarth <howa...@bromo.med.uc.edu> wrote: > On Thu, Apr 15, 2010 at 03:55:07PM -0400, Alexander Hansen wrote: [...] >> That's along the lines of what I was thinking, then--if the svn revision >> were hardcoded into the .info file to guarantee that everybody's >> building against the same revision, then we're replacing the operations: >> >> maintainer pulls from e.g. svn at some revision >> maintainer generates a snapshot tarball from the svn pull >> maintainer puts tarball online >> maintainer updates package description >> at build time, fink downloads the snapshot tarball >> ... >> >> with: >> >> maintainer updates package description >> at build time, fink does the svn pull at the svn revision dictated in >> the .info file >> ... >> >> That seems like a reasonable extension of fink's operations to me. > > Alexander, > This would be the typical use. What I was considering was a > bleeding edge package for folks who wanted to track close to > the svn for particular projects like llvm and dragon-egg but be > automated. Currently MacPorts does this by constantly updating > their upcoming gcc4x package (gcc46 now) to the latest snapshot. > I was thinking of doing this in a completely automated fashion > were the current svn revision at any particular moment could be > used (and likely no one would end up with the same exact package). > Again it is just a convenience for working with the svn but through > fink packages. > Jack
Jack, At the beginning of the thread, you mentioned that you wanted to synchronize several packages to build the same revision. If Alexander's suggestion were implemented, a simple shell script could get the current SVN revision, and update the revision in the info files for the set of packages which build from the same repository. -- - Charles Lepple ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
