A (git) workflow for Debian packaging

martin f krafft madduck at madduck.net
Fri Oct 5 21:49:18 UTC 2007

also sprach Manoj Srivastava <srivasta at debian.org> [2007.10.05.2048 +0100]:
>   a) You have a branch for your ./debian directory, right? In an earlier
>      incantation on this list, you had a debian-dir ancestr that you
>      could inherit from, and thus rapidly deploy changes to ./debian. Is
>      this still the case?

Sort of, I just ended up renaming debian-dir to master. Since that's
the main branch which I will need in all Debian packaging attempts,
I might just settle for the default name.

>         I also have ./debian, which is a child of a parent debian-dir
>         project, which allows me to have a common build setup, and
>         rapidly make changes across all my packages are required (new
>         policy, etc).
>         I also have ./debian/common, a separate project, which is the
>         single location to make changes to the common package building
>         setup.
>  Can git actually handle such a setup? (my understanding was that it can
>  not, but I'll be happy to be proved wrong).

I think it can very well do this. One approach is with submodules,
as Pierre points out. They actually may be perfect for what you're
trying to do, at least for ./debian/common.

The other approach (for ./debian) would simply be another remote
added to your local repo, e.g. debian-dir and then to branch
debiandir off debian-dir/master. In that case, you would be tracking
two separate ancestries in your repo: upstream, and debian-dir, and
they wouldn't know about each other until you merge them at one

Or you could just use debhelper. :)

>         I don't know git well enough yet to have interesting commentary
>  on the rest of the post; but if git has indeed gained the capability to
>  handle nested projects (my ./debian dirs for separate packages havce
>  little to do with the upstream software in thge packages,mbut have a
>  lot in common with each other), then it might be worth spending time to
>  learn git and move on from arch.

On the topic of submodules, you may also like to read the following
two URLs, *after* reading the documentation on submodules:


martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net at madduck
"the intellect is not a serious thing, and never has been.
 it is an instrument on which one plays, that is all."
                                                        -- oscar wilde
spamtraps: madduck.bogus at madduck.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature (see http://martin-krafft.net/gpg/)
Url : http://lists.alioth.debian.org/pipermail/vcs-pkg-discuss/attachments/20071005/eaccc273/attachment.pgp 

More information about the vcs-pkg-discuss mailing list