All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 3/6] New package: python-dpkt
Date: Thu, 05 Jan 2012 11:37:33 +0100	[thread overview]
Message-ID: <4F057D6D.6030500@visionsystems.de> (raw)
In-Reply-To: <20120105111645.2caf8493@skate>

Am 05.01.2012 11:16, schrieb Thomas Petazzoni:
> Le Thu, 05 Jan 2012 11:14:09 +0100,
> Julien Boibessot <julien.boibessot@free.fr> a ?crit :
> 
>> Do somebody ever thought in doing a distutils package infrastructure 
>> that would make the adding of a new python package just a matter of:
>>      $(eval $(call DISTUTILSTARGETS))
>> (or something like that)
> 
> Yeah, we discussed that sometime ago. I think our conclusion was:
> "let's wait to have a few Python packages to see what are the common
> things and then we'll do an infrastructure". I guess we could merge
> Yegor's patches as is and then work on a common infrastructure.

I agree. These package can be merged as they are. In the patch series we have 3 packages all using different installation methods:

dpkt - uses internal distutils and ships no C code
mad - uses internal distutils but a part of it must be cross-compiled
netifaces - uses setuptools on top of distutils, has C code and uses distutilscross to get the code crosscompiled

in the future there will be one more internal tool ditsutils2 https://bitbucket.org/tarek/distutils2/overview

and Chris Lambacher is going to PyCon with following talk: https://us.pycon.org/2012/schedule/presentation/11/

So we should wait a little till the sings will calm down and then make our decision.

Best regards,
Yegor

  reply	other threads:[~2012-01-05 10:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-04 11:29 [Buildroot] [PATCH v5 0/6] Python related changes yegorslists at googlemail.com
2012-01-04 11:30 ` [Buildroot] [PATCH v5 1/6] Python: add external modules option yegorslists at googlemail.com
2012-01-07 19:54   ` Peter Korsgaard
2012-01-04 11:30 ` [Buildroot] [PATCH v5 2/6] Python: enable zlib support for the host package yegorslists at googlemail.com
2012-01-07 19:54   ` Peter Korsgaard
2012-01-04 11:30 ` [Buildroot] [PATCH v5 3/6] New package: python-dpkt yegorslists at googlemail.com
2012-01-05 10:14   ` Julien Boibessot
2012-01-05 10:16     ` Thomas Petazzoni
2012-01-05 10:37       ` Yegor Yefremov [this message]
2012-01-07 19:57   ` Peter Korsgaard
2012-01-04 11:30 ` [Buildroot] [PATCH v5 4/6] New package: python-setuptools yegorslists at googlemail.com
2012-01-07 19:58   ` Peter Korsgaard
2012-01-04 11:30 ` [Buildroot] [PATCH v5 5/6] New package: python-distutilscross yegorslists at googlemail.com
2012-01-07 19:59   ` Peter Korsgaard
2012-01-04 11:30 ` [Buildroot] [PATCH v5 6/6] New package: python-netifaces yegorslists at googlemail.com
2012-01-07 20:00   ` Peter Korsgaard
2012-01-08 11:03     ` Peter Korsgaard
2012-01-09  7:46       ` Yegor Yefremov

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=4F057D6D.6030500@visionsystems.de \
    --to=yegor_sub1@visionsystems.de \
    --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.