Hi,
On Tue, Feb 06, 2018 at 03:50:53PM +0100, IOhannes m zmoelnig wrote:
> Package: git-buildpackage
> Version: 0.9.7
> Severity: wishlist
>
> Dear Maintainer,
>
> thanks for git-buildpackage.
>
> it would be even better, if i could use some veriables in the gbp.conf,
> allowing me to structure the generated output even more.
>
> e.g. i like to put all the output (binary packages, changes-files,...) into a
> separate directory, so they don't clutter my normal file browsing experience.
>
> that's why i have the following in my ~/.gbp.conf:
>
> ~~~
> [buildpackage]
> export-dir = ../build-area/
> ~~~
>
> this works rather nicely, ...but:
> when working with many packages, this either
> - fills the export-dir with many many files, making it unwieldy to find
> anything.
> - OR forces the user to use subdirectories for each package.
>
> traditionally i employed the 2nd option, e.g. having a file structure like
> - .../Debian/somepackage/somepackage/debian/rules
> - .../Debian/otherpackage/otherpackage/debian/rules
>
> which gives me export-dirs like:
> - .../Debian/somepackage/build-area/
> - .../Debian/otherpackage/build-area/
>
> now this requires an awful lot of cd'ing into package/package subdirectories
> (dealing with about
> 100 packages).
>
> so i'd rather have something simple like:
> - .../Debian/somepackage/debian/rules
> - .../Debian/otherpackage/debian/rules
>
> but tell gbp to not put all the output files into .../Debian/build-area/, but
> instead i'd like:
>
> - .../Debian/build-area/somepackage/
> - .../Debian/build-area/otherpackage/
>
> or maybe even
> - .../Debian/build-area/somepackage/2.0/
> - .../Debian/build-area/somepackage/2.1/
> - .../Debian/build-area/otherpackage/1.14/
>
>
> for this to work it would be great if i could use variables in the gbp.conf.
> e.g. something like
>
> ~~~
> [buildpackage]
> export-dir = ../build-area/%(pkg)s
> ~~~
>
> or
>
> ~~~
> [buildpackage]
> export-dir = ../build-area/%(GBP_PACKAGE_NAME)s
> ~~~
>
> i think such variable support can be of general usefulness.
>
> for my personal use cases, i'd be happy if i could pass:
> - package name
> - package upstream version
> - package debian version
That makes sense. I've merged this with a similar bug and I hope to get
around to parts of this during debcamp latest.
Cheers,
-- Guido
