Re: RFC declarative built-using field generation
On Sat, Feb 09, 2013 at 03:42:38AM +0100, Andreas Beckmann wrote:
> Can't we just annotate the foo-source binary package in some way - it
> should be pretty clear to the maintainer that he produces such a
> "special" package. Then for building other packages B-D-ing on the
> "special" package we could have a helper that looks for "annotated"
> installed build-depends and generates Built-Using if needed.
This fails for the case where a particular package tries to do something
extremely weird which means it can't use shared libraries, and therefore
must use the static versions of library packages.
I suppose that package could then pass some option to dh_builtusing to
specify that needs to consider more than just the annotated packages,
but otoh you then wouldn't want that to result in it also declaring a
built-using on debhelper, autotools-dev, and a bunch of other things
that are irrelevant.
This route gets fairly messy fairly quickly, I'm afraid.
Copyshops should do vouchers. So that next time some bureaucracy requires you
to mail a form in triplicate, you can mail it just once, add a voucher, and
save on postage.