UDD health check?

Elliot Murphy elliot at canonical.com
Tue Jul 13 21:20:09 BST 2010


On Tue, Jul 13, 2010 at 4:04 PM, Barry Warsaw <barry at canonical.com> wro
> but it seems to have some advantages for the way I work.

This is cool, thanks for 'splaining.

> Where does your debian/ directory live in the dvcs cloud?  IOW, do you have a
> separate unrelated branch that just includes debian/ and do you push that to
> LP?  Or does that live only in Debian's svn once you've injected it (i.e. you
> only make packaging changes to that directory).

The latter, I only make packaging changes in that directory, I don't
bother with a DVCS cloud version. I have contemplated using bzr-svn to
pull the DPMT SVN repository so that I can diff things without hitting
the network, but haven't done it yet.

> Do you spin PPAs from that
> same debian/ directory or do you make a branch of that to do the PPA changelog
> dance?

I just edit the changelog revision number to put the PPA
~lucid1/~maverick1 style suffixes, build/test/sign/upload, and then
svn revert.

> The debian/ directory is certainly separate, but it's also related.  E.g. when
> you branch an Ubuntu source package, e.g. `bzr branch lp:ubuntu/simplejson`
> what do you get?  A sourceful layout with an embedded debian/ directory.

Yes, and I'm not supposed to directly edit any of the source outside
of debian/, which is why the layout used by svn-buildpackage with only
debian/ in VCS resonates with me. Having said that, the full extracted
source is incredibly useful when I'm debugging - it's nice to be able
to diff a given source file between different package versions which
sometimes don't line up in a meaningful way with upstream VCS (because
they can be patched in the debian package).

-- 
Elliot Murphy | https://launchpad.net/~statik/



More information about the ubuntu-distributed-devel mailing list