Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next] python-certifi: add new package
Date: Wed, 19 Nov 2014 10:57:11 +0100	[thread overview]
Message-ID: <87a93no6mg.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <87ioibodrx.fsf@dell.be.48ers.dk> (Peter Korsgaard's message of "Wed, 19 Nov 2014 08:22:42 +0100")

>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:

Hi,

 >> 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).

After discussing it on IRC we agreed that the extra dependencies inside
the package Config.in doesn't make sense, but we should be consistent
all over the tree, so I will remove the extra depends on lines in next.

Thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2014-11-19  9:57 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
2014-11-19  9:57         ` Peter Korsgaard [this message]
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=87a93no6mg.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