From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2 0/4] python: add simpleRPL package, dependencies and cakes
Date: Sat, 29 Mar 2014 10:03:43 +0100 [thread overview]
Message-ID: <20140329090343.GA10959@pengutronix.de> (raw)
In-Reply-To: <1395777230-16813-1-git-send-email-alex.aring@gmail.com>
On Tue, Mar 25, 2014 at 08:53:46PM +0100, Alexander Aring wrote:
> Hi,
>
> this patch series adds the simpleRPL python implementation into ptxdist.
> This implementation is in a early state of development. I talked with the
> original Author "Tony Cheneau", he doesn't have time anymore to work on
> this implementation. Now, I have some time and will look at this code
> and maybe I do some implementation to that.
>
> There are two questions for me:
>
> i)
>
> The license is a NIST license which describes [1]:
>
> "... As a result, a formal license is not needed to use this software."
>
> I don't add any LICENSE to the rule files, but which is the correct ptxdist
> synonym for a NIST license, but the NIST license says the software has no
> license. I think there is no NIST license and the NIST developers doens't
> release the software under any license.
>
> ii)
>
> I uploaded the software to my cakelab account. I hope that's okay, the
> alternative would be github. But github has a confusing naming style
> at generate releases for software and I can't change them.
>
> I have still access to the cakelab "bakery for gourmets" server and
> I will take care of this that the RPL cakes (the software archives) is still
> there for ptxdist. I know the owner of the cake laboratories.
>
>
>
> There are still some change needed to the buildsystem to work better with
> ptxdist. I will try to do that and will send patches for these rules then.
> For example ("[PATCH 3/4] python-rplicmp: add new package") will call
> $(CROSS_CC) directly.
>
> - Alex
>
> [1] https://github.com/tcheneau/simpleRPL/blob/master/LICENSE.txt
>
> changes since v2:
> - change lib permission in python-rplicmp to 644
> - change lib permission in python-routing to 644
> - add python tag to cover-letter
>
> Alexander Aring (4):
> host-cython: add CROSS_CYTHON_ENV declaration
I've done this a bit differently. I've modified the other patches
accordingly before applying them.
Thanks,
Michael
> python-routing: add new package
> python-rplicmp: add new package
> simplerpl: add new package
>
> rules/host-cython.make | 2 ++
> rules/python-routing.in | 13 ++++++++
> rules/python-routing.make | 74 ++++++++++++++++++++++++++++++++++++++++++++
> rules/python-rplicmp.in | 11 +++++++
> rules/python-rplicmp.make | 75 ++++++++++++++++++++++++++++++++++++++++++++
> rules/simplerpl.in | 13 ++++++++
> rules/simplerpl.make | 79 +++++++++++++++++++++++++++++++++++++++++++++++
> 7 files changed, 267 insertions(+)
> create mode 100644 rules/python-routing.in
> create mode 100644 rules/python-routing.make
> create mode 100644 rules/python-rplicmp.in
> create mode 100644 rules/python-rplicmp.make
> create mode 100644 rules/simplerpl.in
> create mode 100644 rules/simplerpl.make
>
> --
> 1.9.1
>
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2014-03-29 9:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 19:53 Alexander Aring
2014-03-25 19:53 ` [ptxdist] [PATCH v2 1/4] host-cython: add CROSS_CYTHON_ENV declaration Alexander Aring
2014-03-25 19:53 ` [ptxdist] [PATCH v2 2/4] python-routing: add new package Alexander Aring
2014-03-25 19:53 ` [ptxdist] [PATCH v2 3/4] python-rplicmp: " Alexander Aring
2014-03-25 19:53 ` [ptxdist] [PATCH v2 4/4] simplerpl: " Alexander Aring
2014-03-29 9:03 ` Michael Olbrich [this message]
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=20140329090343.GA10959@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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