[Debichem-devel] Bug#522560: ITP: bist -- chemical drawing tool

[David Paleino]

Hello Daniel,

On Sat, 11 Apr 2009 19:14:58 +0200, Daniel Leidert wrote:

> Am Samstag, den 11.04.2009, 15:16 +0200 schrieb David Paleino:
> [..]
> 
> Well, the check_watch_files-script can be fixed to consider the Git repo
> too and AFAIK the PET [1] guys are working on multiple-repo-support too.

Uhm, I am one of those who wanted that too :)

> IMHO having SVN (following the debian-only policy) and Git is absolutely
> perfect. Please just give a short introduction, which issues should be
> avoided using git/git-buildpackage so we can really team-maintain it and
> help you if necessary (IIRC there was something related to rebase?).

Sure I'll do, but probably on a separate thread (or, better, on a separate
document? So that it's useful for other people too)

One great difference from SVN is that each package has its own repository: you
can configure per-package "hooks" (you have those in SVN too, but they're
"global"), and you need to create a repository on Alioth first (i.e. there's
nothing like svn-inject, and this was what first stopped me from adopting Git
months before :) )

> BTW: Does Git now better support the debian-only approach? Or is
> pristine-tar an alternative to the debian-only approach? What is the
> strategy here?

There is people still having debian-only in Git. I can't speak for those, since
I'm using the pristine-tar approach.
There are some nice tools which prefer a pristine-tar layout (namely:
git-import-orig, git-import-dsc, git-buildpackage -- these are what I use, but
there may be others)

The repository layout consists of three branches:
 - master
 - pristine-tar
 - upstream

The "master" branch is the result of merging debian/ with the contents of the
"upstream" branch, which contains the unpacked sources.
The "pristine-tar" branch is only used by tools, and should never be touched by
any human (quite, it happened to me that some actions were needed). These tools
are: git-buildpackage, git-import-*, pristine-tar. The branch contains "delta"
files, which are used to regenerate the .orig.tar.gz tarballs. In some cases,
pristine-tar isn't able to rebuild the original tarball, and that's a bug which
should be filed [0]. In case such a bug occurs, it is sufficient to create
an .orig.tar.gz in a "traditional way" (uscan, get-orig-source, whatever), and
put it into ../tarballs/ (or whatever git-buildpackage is configured to use)

However, if there are people here wanting to use Git, I can write something
more organic, and put a link here :)

> > > If you prefer to maintain bist on your own in collab-maint, that would
> > > be fine as well, of course.
> > 
> > Maintaining it in a team is always good IMVHO :)
> 
> IMHO we have some nice QA-workflow,

Is this documented anywhere? I'm not new to team-work (I'm in *lots* of teams),
and I learnt that each team has its own rules. Is there a "Group Policy"
available anywhere?

> a low bug-count and we are almost always up-to-date. So IMHO debichem is not
> a worst place to put chemistry related Debian packages ;)

Thank you :)

Ciao,
David


[0] http://bugs.debian.org/pristine-tar , see those "failed to regenerate build
of $package" bugs.

-- 
 . ''`.  Debian maintainer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 ----|---- http://snipr.com/qa_page
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/debichem-devel/attachments/20090411/54aaa14a/attachment.pgp>