Source: poppler
Version: 0.22.5-4
Severity: wishlist
Tags: patch
As the subject says: the attached patch adds the possibility to do a
bootstrapping build of poppler at a stage where Gtk+ and Qt are not yet
available.
--
Daniel Schepler
diff -urN poppler-0.22.5.old/debian/rules
tag 738338 - patch
thanks
Hi,
On 2014-02-09 12:37, Daniel Schepler wrote:
As the subject says: the attached patch adds the possibility to do a
bootstrapping build of poppler at a stage where Gtk+ and Qt are not
yet
available.
While I am looking forward to a way to disable frontends in a
On Sunday, February 09, 2014 03:42:50 PM you wrote:
tag 738338 - patch
thanks
Hi,
On 2014-02-09 12:37, Daniel Schepler wrote:
As the subject says: the attached patch adds the possibility to do a
bootstrapping build of poppler at a stage where Gtk+ and Qt are not
yet
available.
On Sunday, February 09, 2014 03:42:50 PM Pino Toscano wrote:
- 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:
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
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
+++ Johannes Schauer [2014-02-09 19:42 +0100]:
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
7 matches
Mail list logo
