Hi everyone,
On Sunday 14 October 2012 20:06:19 Guillem Jover wrote:
> On Sun, 2012-10-14 at 23:12:14 +0200, Jakub Wilk wrote:
> > I'd like to propose the following solution:
> >
> > Let's introduce a new class of standard substitution variables, one
> > for every binary package, expanding to "<source> (= <version>)".
> > Then user could decide which of them use in the Built-Using field.
> > E.g.:
> >
> > Built-Using: ${foocc-source:Source}, ${libbaz-dev:Source}
What about ORed build-dependencies?
Build-Using: ${bar-source:Source} | ${baz-source:Source} ?
It becomes interesting if bar-source and baz-source are co-installable :)
If this use case isn't going to be supported, I think that whatever dpkg-foo
is going to generate the substitutions should check for them (b-u package
has alternatives) and possibly abort. Unless one wants to delegate that to
lintian...
> Probably better something
> like ${Built-Using:pkgname} or ${srcdep:pkgname} (to match shlibs),
> although the former is pretty long and repetitive with the field name,
> maybe better with just ${B:pkgname} mimicking the ${F:fieldname} magic
> substvars. If the package is not installed then we should at least
> warn, or maybe even error out.
How about BU (short for Built-Using) or BS (short for Binary's Source)?
I find a lone B kind of confusing.
Cheers,
--
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
