Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] scanpypi: new utility
Date: Sun, 10 Jan 2016 11:59:50 +0100	[thread overview]
Message-ID: <20160110105950.GA3460@free.fr> (raw)
In-Reply-To: <1438089330-18923-1-git-send-email-denis.thulin@openwide.fr>

Denis, All,

Sorry for the long delay. I'm now having a look at this patch.

On 2015-07-28 15:15 +0200, Denis THULIN spake thusly:
> An utility for creating python package from the python package index
> It fetches packages info from http://pypi.python.org and generates
> corresponding packages files.

So, we currently have scancpan to create perl packages. You are adding
scanpypi to create Python packages. There's also someone who submitted
a script to generate a 'generic' package (i.e. not perl/python) [0].
The scancpan is written in perl, yours and the generic one in Python.

Besides Perl and Python, we also have nodejs which provides a similar
"package-store" and for which it would become interesting to provide a
helper script to generate packages [1].

What I would love to see is that we have a single script to add
packages. Something like:

    $ ./support/script/add-package -t TYPE [OPTS] PKG [PKG...]

with TYPE being one of the package types we currently have (generic,
autotools... python, perl...) or an abstract type (nodejs...).

Then, the cpan, pypi, nodejs... script would be just 'backends' that
would provide classes called by the main script, like;

    pkg = new PythonPkg("foo")
    pkg.get_br_name()       returns the BR2_PACKAGE_ name
    pkg.get_version()       returns the _VERSION string
    pkg.get_source()        returns the _SOURCE string
    pkg.get_site()          returns the _SITE string
    pkg.get_method()        returns the _SITE_METHOD string
    pkg.get_dependencies()  returns the _DEPENDENCIES list
    ... and so on, you get the idea. ;-)

That would also recursively generate the packages for the dependencies,
if not already present.

Of course, that would mean we'd have to standardise on a single
language. I think Python is the way to go here.

Would you be interested in pursuing this?

[0] https://patchwork.ozlabs.org/patch/523257/
[1] that could also require a nodejs-package infra, but not necessarily.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2016-01-10 10:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28 13:15 [Buildroot] [PATCH 1/2] scanpypi: new utility Denis THULIN
2015-07-28 13:15 ` [Buildroot] [PATCH 2/2] python-robotframework: New package Denis THULIN
2015-08-31 15:58 ` [Buildroot] [PATCH 1/2] scanpypi: new utility Denis Thulin
2016-01-10 10:59 ` Yann E. MORIN [this message]
2016-01-10 15:36   ` Arnout Vandecappelle
2016-01-13 15:23     ` Thomas Petazzoni
2016-01-14  8:32       ` Yegor Yefremov
2016-01-27 13:30         ` Yegor Yefremov
2016-02-02 18:02   ` Eelco Chaudron
2016-02-02 19:54     ` Eelco Chaudron
2016-03-01  1:44 ` Carlos Santos
  -- strict thread matches above, loose matches on Subject: below --
2015-07-09 13:31 [Buildroot] [PATCH 0/2] python-package-generator Denis THULIN
2015-07-09 13:31 ` [Buildroot] [PATCH 1/2] scanpypi: new utility Denis THULIN
2015-07-11 12:56   ` Arnout Vandecappelle
2015-07-15 14:08     ` Denis Thulin

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=20160110105950.GA3460@free.fr \
    --to=yann.morin.1998@free.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