mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <r.hieber@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v3 5/7] cups: new package: Common Unix Printing System
Date: Tue, 31 Oct 2017 22:17:59 +0100	[thread overview]
Message-ID: <f88a8720-1c9d-601d-7d90-9195fec56b67@pengutronix.de> (raw)
In-Reply-To: <20171028095403.kj7nxrfbt3a7lmyt@pengutronix.de>

On 28.10.2017 11:54, Michael Olbrich wrote:
> On Wed, Oct 25, 2017 at 10:57:49PM +0200, Roland Hieber wrote:
[...]
>>
>> Notes:
>>     changes in v2 -> v3:
>>      - version bump 2.2.4 -> 2.2.5
[...]
>>
>> diff --git a/patches/cups-2.2.4/0001-configure-allow-explicit-disabling-of-Java-PHP-Perl-.patch b/patches/cups-2.2.4/0001-configure-allow-explicit-disabling-of-Java-PHP-Perl-.patch
>> new file mode 100644
>> index 000000000..f110f5aaa
>> --- /dev/null
>> +++ b/patches/cups-2.2.4/0001-configure-allow-explicit-disabling-of-Java-PHP-Perl-.patch
>> @@ -0,0 +1,92 @@
>> +From: Roland Hieber <r.hieber@pengutronix.de>
>> +Date: Mon, 25 Sep 2017 15:00:16 +0200
>> +Subject: [PATCH] configure: allow explicit disabling of Java/PHP/Perl/Python
>> + support
>> +
>> +Currently, when configure is called with --with-java or --with-java=,
>> +auto-detection is performed. When called with --without-java, HAVE_JAVA
>> +is still being defined. This is unfortunate when cross-compiling for
>> +embedded systems, we would end up with Java on the host being
>> +auto-detected (which is not what we have on the target), or with a wrong
>> +HAVE_JAVA define. We need a way to explicitely disable scripting support
>> +for all supported languages.
>> +
>> +Forwarded: https://github.com/apple/cups/pull/5122
> 
> It seems something was done upstream. Can you cherry-pick those commits
> instead. That will simplify updating later on.

Ah, that was a leftover from 2.2.4, which is already (somehow) included
in 2.2.5 and no longer relevant.

 - Roland

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2017-10-31 21:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-25 20:57 [ptxdist] [PATCH v3 1/7] libpaper: new package: system-wide papersize configuration Roland Hieber
2017-10-25 20:57 ` [ptxdist] [PATCH v3 2/7] qpdf: new package: PDF inspection library and tools Roland Hieber
2017-10-25 20:57 ` [ptxdist] [PATCH v3 3/7] poppler-data: new package: optional encoding data for poppler Roland Hieber
2017-10-25 20:57 ` [ptxdist] [PATCH v3 4/7] poppler: version bump 0.18.0 -> 0.59.0 Roland Hieber
2017-10-25 21:15   ` Roland Hieber
2017-10-28  9:46   ` Michael Olbrich
2017-10-25 20:57 ` [ptxdist] [PATCH v3 5/7] cups: new package: Common Unix Printing System Roland Hieber
2017-10-27 17:54   ` Michael Olbrich
2017-10-31 22:31     ` Roland Hieber
2017-11-01 10:45       ` Michael Olbrich
2017-10-28  9:54   ` Michael Olbrich
2017-10-31 21:17     ` Roland Hieber [this message]
2017-10-25 20:57 ` [ptxdist] [PATCH v3 6/7] host-cups: new package: CUPS host tools Roland Hieber
2017-10-28  9:57   ` Michael Olbrich
2017-10-25 20:57 ` [ptxdist] [PATCH v3 7/7] cups-filters: new package: additional filters and backends for CUPS Roland Hieber
2017-11-01 10:51 ` [ptxdist] [PATCH v3 1/7] libpaper: new package: system-wide papersize configuration Michael Olbrich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f88a8720-1c9d-601d-7d90-9195fec56b67@pengutronix.de \
    --to=r.hieber@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox