Skip to content

Introduce New Package PySnmp

Thomas Petazzoni buildroot 1 version New

Get series with b4
b4 am 20131003231552.123a5212@skate

Versions newest first

  1. v1 Latest1 of 5 patches 0 repliesNew

1 of 5 patches is in this archive. The cover letter announces 5.

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/5python-pyasn: new package+0 -01 reply

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [Buildroot] [PATCH 0/5] Introduce New Package PySnmp

Dear Ryan Barnett,

Quoted 15 lines · Ryan Barnett

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

Quoted 5 lines

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

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