Public SourceMage Discussion List

[Eric Sandall <eric AT sandall.us>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 17 Aug 2005, Sergey A. Lipnevich wrote:
> I'm also against version to be set to current date. We had that
> disagreement with David when discussing httpd-dev spell. I think setting
> version to a constant (e.g. I prefer HEAD as a name of "latest" revision
> in CVS and Subversion) and using FORCE_DOWNLOAD=on is the best
> combination of choice and convenience. It has just one disadvantage: no
> way to go to previous version by using "dispel -d". This is minor though
> because the source taken from repository is more likely to not build
> than to build and not work.
> VERSION=$(date ...) is a clever hack and has the right to exist, but
> only as *non-default* spell configuration option, IMO.
>
> Sergey.
>
> On Wed, 2005-08-17 at 21:12 +0200, Andrew "ruskie" Levstik wrote:
> > > >   VERSION=$(date +%Y%m%d) should be set both if auto-update is
> > > >   wanted or not.
> > >
> > > This could only work if FORCE_DOWNLOAD is off for the non-auto update ones
> > > of course, but even then wouldn't this cause the non-auto update ones to
> > > think they have a new version each day they come up in a cast, then just
> > > recast the exact sources they already have?
> >
> > IMHO NO(I feel very strongly about this) I don't like to use some random thing
> > to set a version. I prefer for the VERSION=[whatever_scm_it_uses] approach
> > for non automatic(i.e. VERSION=cvs, VERSION=svn and so on).
> >
> > Who came up with the idea for using date for both...
> >
> > And yeah for FORCE_DOWNLOAD it should be clearly documented if it's used this
> > or that way.

Just FYI to end this part of the thread: The user will get to choose
whether they have a variable VERSION or static, if there is an option
(e.g. if using CVS they can choose to use date-based or tag-based).
So, you can choose whichever floats your boat when you cast.
Personally, I prefer the date option, but obviously not everyone
shares that opinion. Allowing the option satisfies both camps and I'm
not sure why this keeps coming up after we've already settled on a
solution that works.

- -sandalle

- --
Eric Sandall                     |  Source Mage GNU/Linux Developer
eric AT sandall.us                  |  http://www.sourcemage.org/
http://eric.sandall.us/          |  SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/  #196285  |  http://www.shock.wsu.edu/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDA9E7HXt9dKjv3WERAmX/AKDEYddv8ILj1haqT0v06X5fyaiRkwCguTS9
JVCrJOqmt16xpYCK/xsU4vQ=
=0Nnu
-----END PGP SIGNATURE-----