[Pkg-ayatana-devel] packaging repository

Evgeni Golov evgeni at debian.org
Sun Jun 3 08:28:06 UTC 2012


On Sat, Jun 02, 2012 at 04:03:24PM -0400, Andrew Starr-Bochicchio wrote:
> On Sat, Jun 2, 2012 at 1:38 PM, Ritesh Raj Sarraf <rrs at researchut.com> wrote:
> > Hello Folks,
> >
> > Does the repo need to be bzr only or can I put something in under
> > /git/pkg-ayatana ?
> > Please let me know either ways. I am okay to put it under collab-maint also.
> >
> > Just that, in the past, I've kept mixing commands from the one to the
> > other. And also just want to use/learn one, and do it good.
> Hi,
> I'm not sure if it is considered policy, but using bzr has certainly
> been a best practice. As both the upstream project and Ubuntu use bzr,
> using it allows us to have shared history with both the upstream
> branch as well as the Ubuntu packaging branch. This makes merging
> changes and cherry picking patches between the different projects very
> easy. Though if you feel strongly about using git, I guess you could
> go ahead. This isn't a particularly tight knit team.
> Any one else feel strongly one way or the other?

Same here. I'd neither call it policy, but using bzr makes things way 
easier (even when bzr sucks :)).
Being able to branch and merge the Ubuntu packaging directly is worth it 
imho.  My usual package updates look like this:
cd package/ubuntu && bzr pull && cd ../debian && bzr merge ../ubuntu && 
(resolve possible conflicts &&) bzr commit
takes less then 5 minutes usually :)

you also could try https://github.com/termie/git-bzr-ng

or just use git, noone will kill you :)


Bruce Schneier can read and understand Perl programs.

More information about the Pkg-ayatana-devel mailing list