All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] imagemagick: disable documentation
Date: Sun, 02 Mar 2014 11:45:55 +0100	[thread overview]
Message-ID: <53130BE3.8080904@openwide.fr> (raw)
In-Reply-To: <20140302002238.2eb2d717@skate>

Hi Thomas,

Le 02/03/2014 00:22, Thomas Petazzoni a ?crit :
> Dear Romain Naour,
>
> On Sun, 16 Feb 2014 00:57:47 +0100, Romain Naour wrote:
>> There is no options to disable the documentation,
>> so remove it directly in Makefile.am
>>
>> Signed-off-by: Romain Naour <romain.naour@openwide.fr>
>> ---
>>   .../imagemagick/imagemagick-02-disable-doc.patch   | 47 ++++++++++++++++++++++
>>   1 file changed, 47 insertions(+)
>>   create mode 100644 package/imagemagick/imagemagick-02-disable-doc.patch
> Can you have a look at implementing the solution proposed by Arnout
> (i.e adding a --disable-docs or --disable-documentation configure
> option) ?

Not yet, but it's in my todo list.
I'll do it as soon as possible but I have another task to finish before.

> Also, it would be really great if you could push this patch, as well as
> the other patch we already have against imagemagick, to the upstream
> project.
This is what I planned to do :)

Best regards,
Romain

      reply	other threads:[~2014-03-02 10:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-15 23:57 [Buildroot] [PATCH 1/2] imagemagick: disable documentation Romain Naour
2014-02-15 23:57 ` [Buildroot] [PATCH 2/2] imagemagick: use --without-bzlib when bzip2 is not selected Romain Naour
2014-02-26  8:47   ` Peter Korsgaard
2014-02-17 21:23 ` [Buildroot] [PATCH 1/2] imagemagick: disable documentation Arnout Vandecappelle
2014-02-17 22:15   ` Romain Naour
2014-02-17 23:07     ` Arnout Vandecappelle
2014-03-01 23:22 ` Thomas Petazzoni
2014-03-02 10:45   ` Romain Naour [this message]

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=53130BE3.8080904@openwide.fr \
    --to=romain.naour@openwide.fr \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.