From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next] python-certifi: add new package
Date: Wed, 19 Nov 2014 08:22:42 +0100 [thread overview]
Message-ID: <87ioibodrx.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20141119000429.65c6a8c3@free-electrons.com> (Thomas Petazzoni's message of "Wed, 19 Nov 2014 00:04:29 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
>> > We need a depends on BR2_PACKAGE_PYTHON || BR2_PACKAGE_PYTHON3 here. I
>> > know it's not very useful since Python packages can anyway only be
>> > selected when either Python or Python 3 are enabled, but we have this
>> > conditional for all Python packages, so we should remain consistent and
>> > have it there as well.
>>
>> Well, a quick grep in next shows that we have 8 packages without this depends,
>> and 14 packages with the depends.
>>
>> However, since the python packages that have recently been added by Peter do
>> not have the depends, and since he told Yegor to remove the depends in
>> python-webpy, I think the rule now is _not_ to have the depends.
> Damn, so the guy doing most of the Python maintenance, and who did
> introduce the possibility of building modules with both Python 2 and
> Python 3, doesn't have a word into such decisions? Where are we
> going? :-)
Everything is open for discussion, but why would you want to add it?
Consistency?
To me it makes pretty good sense that the modules are only visible if
python || python3, and the individual modules can add further
restrictions if needed (only for python2 or python3, needing some other
package or toolchain options).
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-11-19 7:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 20:20 [Buildroot] [PATCH next] python-certifi: add new package Yegor Yefremov
2014-11-18 22:07 ` Thomas Petazzoni
2014-11-18 22:23 ` Arnout Vandecappelle
2014-11-18 23:04 ` Thomas Petazzoni
2014-11-19 7:22 ` Peter Korsgaard [this message]
2014-11-19 9:57 ` Peter Korsgaard
2014-11-19 7:20 ` Peter Korsgaard
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=87ioibodrx.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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