[Pkg-blender-maintainers] Moving away from CVS? (Was: Blender 2.45 backport for etch)

Cyril Brulebois cyril.brulebois at enst-bretagne.fr
Wed Dec 5 23:06:48 UTC 2007


On 21/10/2007, Florian Ernst wrote:
> I concur that uploading an up-to-date blender to backports as reasoned
> below by Cyril is a fine idea.

Hi again,

I hope you're doing fine since it's been a while since I last heard from
you (and got no answer to my private mail either). If you're busy/afk or
whatever, I could proceed by asking someone else to upload the package
to backports.org.

BTW, I'm really tired of CVS, so I run a git-cvsimport and start hacking
in my blender git repository, available on alioth on [1]. Since I've
been the only one to commit lately, I'd tempted to move the habits to
mine (using pysupport, remember the pycentral-related bug waves last
time?; quilt; git). I don't want to impose it to you anyway if you don't
feel like it and/or want to keep things the way they were until now. I
can imagine being able to deal with pushing this or that diff back to
CVS from time to time, but that looks very suboptimal to me.

Waiting for you to speak up. ;-)

In case you're OK with the idea, since pkg-blender is only maintaining a
single package, I'd be tempted not to ask for the creation of a
pkg-blender.git directory on git.debian.org, but simply putting it
inside the collab-maint directory.  Any DD can commit there, as well as
people added to this group (like I have been some months ago).

 1. http://git.debian.org/?p=users/kibi-guest/blender.git;a=summary


Note that using git allows for tagging versions, as well as working with
branches (tracking the backports or experimental uploads is way easier,
I've experienced that with graphviz), as well as working while
disconnected (that has become a MUST for me), having the whole history
every time, and having a sane way to deal with source code (unlike cvs,
svn, but YMMV).

If you need a crash course, I can provide you with several links, or
even summarize basic worflow (à la CVS) in a short mail.


Also, I've been doing some cleanup, especially WRT to FHS-compliance
lately. I've also added a mechanism to allow other packages (like my
sunflow package) to ship blender scripts, automatically visible from
within blender. (Using /usr/share/blender/scripts.d/$package.)

To check the whole diff between 2.45-1 and the current “trunk”-like:
$ git://git.debian.org/git/users/kibi-guest/blender.git blender.git
$ cd blender.git
$ git-log 2.45-1..
$ git-diff 2.45-1..


Any comment, remark, and the like are very welcome.

Cheers,

-- 
Cyril Brulebois
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-blender-maintainers/attachments/20071206/6e4eb41b/attachment.pgp 


More information about the Pkg-blender-maintainers mailing list