Hi,
On 2014-02-09 19:42, Johannes Schauer wrote:
Quoting Daniel Schepler (2014-02-09 19:13:01)
On Sunday, February 09, 2014 03:42:50 PM Pino Toscano wrote:
> While I am looking forward to a way to disable frontends in a
clean way, your
> patch is for sure not acceptable to me:
> - I don't see DEB_BUILD_PROFILES documented anywhere in Policy, so
I have no
> idea what it is supposed to be, and what tools are supposed to
do with it
> (and neither you describe it, other than "pick this patch"...)
This fairly recently made its way into dpkg, so it's not documented
in policy
yet. The dpkg man pages (dpkg-buildpackage's new -P flag in
particular) and
the blog at https://blog.mister-muffin.de/2014/02/06/botch-updates/
are
currently the existing documentation.
There is a bit more documentation. Here is the current spec of what
we want to
become policy:
https://wiki.debian.org/BuildProfileSpec
Sounds nice and dandy, but that is not Policy yet.
The most important part of this (the new dependency syntax) entered
dpkg 1.17.2
already but we can't upload packages with that syntax yet because
full support
for it needs to arrive in stable as Daniel already pointed out.
> - excluding packages (-Nfoo -Nbar ...) is quite ugly, feels like a
bad hack
> than a well-designed solution
Hi, Johannes.
Maybe you could comment on this: is there any planned way to be able
to
specify something like
Package: libpoppler-libqt4-4
Architecture: any
Profiles: !profile.stage1
...
in debian/control and then have debhelper commands skip those
packages when
appropriate? It would also be nice to have dpkg-genchanges
in-debian-control-
but-not-built warnings not show up for such packages.
Yes. As per the spec I linked to above, the Build-Profiles field in
binary
package stanzas in debian/control is supposed to inform the involved
tools
about which packages build or do not build when a certain build
profile is
enabled. We do not have a patch for debhelper and dpkg-genchanges for
this yet.
Wookey: is does such a patch already exist somewhere?
Pino: src:poppler is one of the ~60 source packages which, if they
were
modified, would make all of Debian bootstrappable.
[...]
Yes, I perfectly know that. I knew that even way before Wookey did his
talk at DebConf a couple of years ago about this (even mentioning
poppler), and most probably even way before you did this research work.
Please leave this bugreport open until this has been further
documented and
implemented in the respective tools.
Please read the last paragraph in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738338#10
which Daniel did not quote when replying further.
In short: I will *not* accept any such hack until:
- there are clean solutions for dependencies and binary packages
- *all* the tools in stable support whatever is the syntax for such
stuff
- the Debian Policy decribes everything (no out-of-Policy tricks)
--
Pino Toscano
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
