> There will be a new command "tarball", which creates the orig.tar.gz, the parameter
> is the version. The build command will be at the end and will create the debian package.
> The version is there as parameter. This format would help to split the recipe part from
> the Debian packaging part.
I would prefer it to be more automatic than that, and make use of the same functionality
as bzr-builddeb.
Something like this should work:
1. Find the final version number that will be used.
2. Take the upstream part of this.
3. Look for a tag in the same way as bzr-builddeb. If it exists:
- Use pristine-tar to provide the tarball
If it doesn't:
- Build a native package.
4. This would mean that you had to use merge-upstream from bzr-builddeb at some point
as well as changing the version number in the recipe. With Rob's {debupstream} expansion
this would be automatic if you are managing the packaging branch with bzr-builddeb.
> BTW, what happens to a package that uses 3.0 (quilt) as source format?
> Then dpkg-source will fail without a source tarball.
Yes, I think you are right about that. That's tricky to workaround without fixing
this bug.
> I would like to see orig.tar.gz building support. What do you think about changing
> the recipe format to something like that:
> # bzr-builder format 0.3
> lp:bzr
> merge fix-build lp:~bzr/bzr/fix-build tarball 1.0+{time}
> merge packaging lp:~bzr/bzr/packaging build 1.0+{time}-0ubuntu1
> There will be a new command "tarball", which creates the orig.tar.gz, the parameter
> is the version. The build command will be at the end and will create the debian package.
> The version is there as parameter. This format would help to split the recipe part from
> the Debian packaging part.
I would prefer it to be more automatic than that, and make use of the same functionality
as bzr-builddeb.
Something like this should work:
1. Find the final version number that will be used.
2. Take the upstream part of this.
3. Look for a tag in the same way as bzr-builddeb. If it exists:
- Use pristine-tar to provide the tarball
If it doesn't:
- Build a native package.
4. This would mean that you had to use merge-upstream from bzr-builddeb at some point
as well as changing the version number in the recipe. With Rob's {debupstream} expansion
this would be automatic if you are managing the packaging branch with bzr-builddeb.
Thanks,
James