Hi Daniel and Pino, 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 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. You can see details about that here: https://bootstrap.debian.net/source/poppler.html (choose a version) Under the section "Cycles" you see that src:poppler is involved in many small cycles where src:poppler is one of the two possible source packages to break the cycle. Under the section "Amount of Cycles through Edges" you see that if src:poppler could be built without libgtk2.0-dev then at least 50 cycles would be broken immediately. Under the section "Feedback Arc Set" you see that src:poppler's build dependencies on libgtk2.0-dev and libqt4-dev are part of the few edges of the dependency graph which would make it completely acyclic. Please leave this bugreport open until this has been further documented and implemented in the respective tools. The ability to build src:poppler with fewer build dependencies plays an important role in making Debian bootstrappable. cheers, josch -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
