[Bf-committers] Blender 2.?? FreeBSD official port
Kent Mein
mein at cs.umn.edu
Wed Jan 12 16:48:17 CET 2011
In reply to Campbell Barton (ideasman42 at gmail.com):
>
> When we do releases we should do this but sometimes nobody does it.
>
> Arch linux package spec also complains of this...
> # Apparently, the blender guys refuse to release source tarballs for
> # intermediate releases that deal mainly with binaries but incorporate tiny
> # minor changes from cvs. Since I'm sick and tired of the urges of users that
> # look for release numbers only we make a messy PKGBUILD that can checkout cvs
> # tags if necessary.
>
> I'm not sure who's responsible for uploading source for releases,
> if nobody else wants to I can make a script to upload exported source
> tree and upload on release.
>
I've done them a lot of the times. I know I haven't done all of them
though. I haven't really been on top of it, because we sometimes
do multiple builds of things and its easier to wait a day or two before
making it.
I wouldn't say it's my offical job, but I've tried to make sure its there
every release, and the only times I haven't done it, are when someone
else has done it first.
It's maybe been questionable to do them on alpha's or betas but if you
look at the source dir I think we have one for every single release we
have had.
Honestly thought I wonder if we really should be doing them at all anymore.
I guess if people still want them, but I know I haven't used a tarball
of blender for at least 8 years. I's say they are a waste of space at
this point. Our svn tree is online and has clear tags for releases.
Kent
--
mein at cs.umn.edu
http://www.cs.umn.edu/~mein
More information about the Bf-committers
mailing list