Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick <kpa_info@yahoo.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] Python 3, simple, external package support
Date: Tue, 12 Feb 2013 16:49:33 +0100	[thread overview]
Message-ID: <511A648D.1060006@yahoo.fr> (raw)
In-Reply-To: <20130212162922.7e940756@skate>

Dear Thomas,

On 02/12/2013 04:29 PM, Thomas Petazzoni wrote:
> Dear Patrick,
>
> On Tue, 12 Feb 2013 16:20:53 +0100, Patrick wrote:
>
>> Thomas, I am aware that there is others packages that depends on
>> host-python, mostly x11. But I have not changed the way host-python nor
>> host-python3 are build and used. I don't understand how the changes I
>> have made could break this compared as previously ? If I'm not mistaken,
>> host-python is selected directly by the package (mesa3d for example)
>> when needed, and this is independent of the selected python package, right ?
>
> True.
>
> So we might end up with two versions of Python installed in
> $(HOST_DIR): python2 and python3. Hopefully, it should work.
>

This is already the case if I enable python3, no ?

> Regarding the patch set, I think I would prefer to rename the current
> python package to python2, and have the 'python' package be the virtual
> package that provides either python2 or python3. That's indeed more
> work, but I find the name "python-generic" not so great.

I have tried like you suggest, but then I have to rename python.mk to 
python2.mk and then any occurrence of python or host-python to python2 
and host-python2 in many package dependencies, no ?

But I could rename python-generic to python-common or something like that ?

      reply	other threads:[~2013-02-12 15:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 14:13 [Buildroot] [PATCH v2] Python 3, simple, external package support Patrick Gerber
2013-02-12 14:13 ` [Buildroot] [PATCH 1/5] Python menu reorganization Patrick Gerber
2013-02-12 14:13 ` [Buildroot] [PATCH 2/5] Add python3 to python simlinks in staging Patrick Gerber
2013-02-12 14:46   ` Samuel Martin
2013-02-12 14:13 ` [Buildroot] [PATCH 3/5] Add common declaration to ease the support of both version Patrick Gerber
2013-02-12 14:14 ` [Buildroot] [PATCH 4/5] python-bottle: Convert package to be used with python2 or python3 Patrick Gerber
2013-02-12 14:20   ` Thomas Petazzoni
2013-02-12 14:14 ` [Buildroot] [PATCH 5/5] python-serial: " Patrick Gerber
2013-02-12 14:21 ` [Buildroot] [PATCH v2] Python 3, simple, external package support Thomas Petazzoni
2013-02-12 14:42   ` Patrick
2013-02-12 14:53     ` Thomas Petazzoni
2013-02-12 15:20       ` Patrick
2013-02-12 15:29         ` Thomas Petazzoni
2013-02-12 15:49           ` Patrick [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=511A648D.1060006@yahoo.fr \
    --to=kpa_info@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox