Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/python-pillow: new package
Date: Wed, 28 Oct 2015 22:20:29 +0100	[thread overview]
Message-ID: <56313C1D.8090001@mind.be> (raw)
In-Reply-To: <CA+TH9VnZK+_B-mnJDdDqWAAXwAFM0722s2ZRmzbwWdjfyawPzw@mail.gmail.com>

On 23-10-15 12:37, Angelo Compagnucci wrote:
> Dear Thomas Petazzoni,
> 
> 2015-10-23 10:22 GMT+02:00 Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com>:
[snip]
>> However, I believe you shouldn't declare any of those options. Just
>> remove them from the Config.in, and use "implicit optional
>> dependencies": i.e python-pillow will have jpeg support if the jpeg
>> package is enabled.
> 
> No problem here, but how can a user detect if a dependency will be
> compiled if he's not informed explicitly about that dependency? A user
> should read the INSTALL file distributed with the software?

 No, the user should read the Config.in help text. In other words, just add a
list there of the libraries that you can select. Something like:

	  Pillow relies on external libraries to provide support various
	  image formats. Select the corresponding package(s) to get this
	  support. Pillow can use jpeg, zlib (for PNG), tiff, freetype, webp,
	  and openjpeg (JPEG-2000).

> 
> Making options explicit makes clear that if I want wepb support I
> should mark the corresponding checkbox.
> 
> In this case the software installer is smart to detect installed
> libraries, but in another case we should have provided build options
> explicitly. Where's the difference? (this is a honest question, just
> for understand the rule!)

 The idea is that we only add package options for non-obvious optional
dependencies. For example, that the jpeg library adds jpeg support to pillow is
quite obvious.

 We don't want to add new config options everywhere because that would really
explode the number of config options.


 Regards,
 Arnout


[snip]

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

      reply	other threads:[~2015-10-28 21:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22 21:25 [Buildroot] [PATCH v2] package/python-pillow: new package Angelo Compagnucci
2015-10-23  8:22 ` Thomas Petazzoni
2015-10-23 10:37   ` Angelo Compagnucci
2015-10-28 21:20     ` Arnout Vandecappelle [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=56313C1D.8090001@mind.be \
    --to=arnout@mind.be \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox