From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/2] New package: python-dpkt
Date: Wed, 21 Dec 2011 09:38:30 +0100 [thread overview]
Message-ID: <20111221093830.1440d9a0@skate> (raw)
In-Reply-To: <4EF19726.3070605@visionsystems.de>
Le Wed, 21 Dec 2011 09:21:58 +0100,
Yegor Yefremov <yegor_sub1@visionsystems.de> a ?crit :
> What would speak against compiling host-python with zlib support? I
> think we'll need it for host-setuputils anyway. AFAIK python-dpkt
> seems to be neglected for quite a while. Though I submitted a bug
> report: http://code.google.com/p/dpkt/issues/detail?id=82, I don't
> think it will be accepted shortly.
>
> Should I prepare a patch for host-python with zlib support?
Adding zlib support in host-python just because dpkt includes itself in
its setup.py script is silly. If all packages do that, then we'll end
up adding cairo support in host-python, just because some Python module
relying on cairo includes itself in its setup.py script.
That said, if zlib support in host-python is needed for
host-setuputils, then it's a different story and zlib support can be
enabled in host-python. But I definitely don't want the host-python to
be cluttered with more and more things simply because some packages do
silly stuff in their setup.py.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-12-21 8:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 15:38 [Buildroot] [PATCH v3 2/2] New package: python-dpkt yegorslists at googlemail.com
2011-12-21 6:54 ` Arnout Vandecappelle
2011-12-21 8:13 ` Thomas Petazzoni
2011-12-21 8:21 ` Yegor Yefremov
2011-12-21 8:38 ` Thomas Petazzoni [this message]
2011-12-21 8:48 ` Yegor Yefremov
2011-12-21 21:18 ` Yegor Yefremov
2011-12-21 22:25 ` Thomas Petazzoni
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=20111221093830.1440d9a0@skate \
--to=thomas.petazzoni@free-electrons.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 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.