[Bf-committers] libraries and release tagging

Martin Poirier theeth at yahoo.com
Sat Jun 5 21:56:27 CEST 2010

Even if the libs themselves aren't tagged, anyone who wants to build a past release can just do a checkout of the lib tree with the revision matching the release tag.

Look there [1], you can easily see what revision matches each release, than you can just do

svn checkout --revision <NUMBER> https://svn.blender.org/svnroot/bf-blender/trunk/lib

[1] http://projects.blender.org/plugins/scmsvn/viewcvs.php/tags/?root=bf-blender

I really don't feel like a tag is needed, to be honest.


--- On Sat, 6/5/10, Tom M <letterrip at gmail.com> wrote:

> From: Tom M <letterrip at gmail.com>
> Subject: [Bf-committers] libraries and release tagging
> To: "bf-blender developers" <bf-committers at blender.org>
> Received: Saturday, June 5, 2010, 3:23 PM
> Hi all,
> it seems like we haven't been tagging libraries with
> releases.  So
> when we do library version changes or removals we are
> likely breaking
> building of older versions of Blender, including our
> current official
> release.
> Is there a way to 'retroactively' tag the library with past
> versions?
> If so might be a good idea.
> LetterRip
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers

More information about the Bf-committers mailing list