Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/5] Introduce New Package PySnmp
Date: Thu, 3 Oct 2013 23:15:52 +0200	[thread overview]
Message-ID: <20131003231552.123a5212@skate> (raw)
In-Reply-To: <1380830465-16083-1-git-send-email-rjbarnet@rockwellcollins.com>

Dear Ryan Barnett,

On Thu, 3 Oct 2013 15:01:00 -0500, Ryan Barnett wrote:
> This patchset adds support for building PySnmp. One thing that I'm not
> sure on and am open to debate is the naming of the packages under
> Target Packages > Interpreter languages and scripting > external python
> modules in the menuconfig since the majority of the packages are named
> python-<pkg_name> but pygame and pyparsing don't fall under this
> category.
> 
> Menuconfig
>  -> python-nfc
>  -> python-protobuf
>  -> pygame
>  -> pyparsing
>  -> python-pyro
>  -> python-pyzmq
> 
> The make rules for the pygame and pyparsing packages are python-pygame
> python-pyparsing.
> 
> Location of the packages in buildroot is package/python-pygame and
> package/python-pyparsing.

Aaah, I now understand better what you were mentioning on IRC. Sorry
for not understanding earlier. I did understand that the name of the
package was "pyparsing", i.e that it was located in package/pyparsing/.
But indeed, it is located in package/python-pyparsing/, so the package
name is 'python-pyparsing'. The only thing that doesn't match is the
Config.in option prompt, and this is not nice.

So clearly, I'm all for changing the Config.in option name, i.e:

-	bool "pyparsing"
+	bool "python-pyparsing"

Thanks, and sorry again for the misunderstanding,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2013-10-03 21:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-03 20:01 [Buildroot] [PATCH 0/5] Introduce New Package PySnmp Ryan Barnett
2013-10-03 20:01 ` [Buildroot] [PATCH 1/5] python-pyasn: new package Ryan Barnett
2013-10-03 21:17   ` Thomas Petazzoni
2013-10-03 22:39     ` Ryan Barnett
2013-10-03 20:01 ` [Buildroot] [PATCH 2/5] python-pycrypto: " Ryan Barnett
2013-10-03 20:24   ` Ryan Barnett
2013-10-03 20:01 ` [Buildroot] [PATCH 3/5] python-pysnmp: " Ryan Barnett
2013-10-03 20:01 ` [Buildroot] [PATCH 4/5] python-pysnmp-apps: " Ryan Barnett
2013-10-03 20:01 ` [Buildroot] [PATCH 5/5] python-pysnmp-mibs: " Ryan Barnett
2013-10-03 21:15 ` Thomas Petazzoni [this message]
2013-10-03 21:21   ` [Buildroot] [PATCH 0/5] Introduce New Package PySnmp Ryan Barnett
  -- strict thread matches above, loose matches on Subject: below --
2013-10-04  1:12 Ryan Barnett
2013-10-04 14:25 ` Ryan Barnett

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=20131003231552.123a5212@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox