Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] How to handle multi-version spells

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Arwed von Merkatz <v.merkatz AT gmx.net>
  • To: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] How to handle multi-version spells
  • Date: Thu, 18 Aug 2005 12:24:59 +0200

On Wed, Aug 17, 2005 at 02:58:39PM -0500, Jeremy Blosser (emrys) wrote:
> On Aug 17, Ladislav Hagara [ladislav.hagara AT unob.cz] wrote:
> > > 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).
> >
> >
> > It was discussed several times.
> > The VERSION=$(date +%Y%m%d) is the only way as to ensure the sources will
> > be updated for normal users. Not all our users are linux specialists,
> > they only want to use their favourite application. They use Source Mage
> > because we provide CVS version of that application.
>
> I'm not trying to reopen the conversation (unless it needs to happen), but
> I thought the below was the original goal Arwed posted for VERSION, and
> what I included in the doc. Arwed if we do want something different now
> please explain:
>
> "If the spell is not set to automatically update, VERSION should be set
> to a constant string (e.g. HEAD, TRUNK). If the spell is set to
> automatically update VERSION should be set to $(date +%Y%m%d). This will
> lead to a new cache tarball every time the spell is updated which is
> intentional. If an automatic update broke something, the user can dispel
> -d to a previous version."

You're right, sorry for starting that discussion again. So the only part
missing is the warning about dependees. Imho you can publish the article
like this and I'll add that note.

--
Arwed v. Merkatz Source Mage GNU/Linux developer
http://www.sourcemage.org




Archive powered by MHonArc 2.6.24.

Top of Page