=== nisscrooge is now known as nisstyre
=== G4MBY is now known as PaulW2U
=== beuno_ is now known as beuno
=== kirkland` is now known as kirkland
=== jrwren_ is now known as jrwren
[17:34] <al_exquemelin> I was wondering how to get my code from a bzr branch into a .tar.gz archive? and do I really need the latter to build a PPA package?
[17:35] <al_exquemelin> I've looked through the Ubuntu Packaging guide but still don't quite get it
[17:42] <hjd> al_exquemelin: The launchpad PPA builders can build packages directly from a bzr branch (assuming it is set up for packaging with a debian directory etc).
[17:43] <hjd> If you wish to build it yourself, bzr-builddeb should work (I think it maybe generates the .tar.gz behind the scenes, but it too only needs the branch in order to work)
[17:48] <al_exquemelin> hjd: didn't add the /debian directory as yet, it seems I'll have to investigate the description for it
[17:50] <al_exquemelin> hjd: but where do I start with building my PPA packages? writing a recipe first?
[17:51] <hjd> The packaging guide contains a quick overview of the debian/ directory http://packaging.ubuntu.com/html/debian-dir-overview.html
[17:52] <al_exquemelin> hjd: yes, I've seen it, thanks
[17:56] <hjd> Depends what you have done so far. Presumably you have some bzr branch with a piece of software? I don't know how the packaging guide is structured, but I think a natural first step would be to make it possible to build package(s) from it locally and then do that first.
[17:58] <hjd> The PPA recipe will list the branch (or branches more of you wish to combine) you need in order to build a package, but will require that the branch is actually able to produce a package.
[17:58] <hjd> :)
[17:59] <hjd> Does that make sense?
[18:08] <al_exquemelin> hjd: yes, I guess I'll start with filling up the /debian directory