From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: FW: [oe] [meta-oe][PATCH] parted_1.8.6.bb: add parted that not GPLv3
Date: Tue, 07 Jul 2015 16:55:40 +0300 [thread overview]
Message-ID: <559BDA5C.6060905@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LY5fEmX8Of5d2prJ01fHvf7LV170qTz+r1kd0vtkGgesQ@mail.gmail.com>
On 07/07/2015 04:38 PM, Burton, Ross wrote:
> How about renaming the recipe, so that it doesn't clash with the
> GPLv3 version? For example, parted1_1.8.6.bb
> <http://parted1_1.8.6.bb>. Then it can be kept outside of oe-core.
>
>
> As they're just version variations that would be overly complex.
> Dropping it in oe-core as it's a non-v3 alternative doesn't seem to be a
> problem to me (as there's plenty of precedent for that already).
My problem is that parted 1.8.6 was released in 2007, and the recipe
already carries eight patches with it (and none of them has any
information about their origin).
Who's going to provide ongoing maintenance for all that? I would like
Lei to establish himself as the maintainer (through the maintainers.inc
file).
Regards,
Alex
next prev parent reply other threads:[~2015-07-07 13:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 1:51 [meta-oe][PATCH] parted_1.8.6.bb: add parted that not GPLv3 Lei Maohui
2015-07-06 22:22 ` Andre McCurdy
2015-07-07 3:50 ` FW: [oe] " Lei, Maohui
2015-07-07 8:18 ` Burton, Ross
2015-07-07 13:30 ` Alexander Kanavin
2015-07-07 13:38 ` Burton, Ross
2015-07-07 13:55 ` Alexander Kanavin [this message]
2015-07-07 13:59 ` Otavio Salvador
2015-07-08 9:18 ` Lei, Maohui
2015-07-09 0:43 ` Lei, Maohui
2015-07-08 9:26 ` Lei, Maohui
2015-08-31 17:58 ` Martin Jansa
2015-08-31 19:11 ` Andre McCurdy
2015-08-31 19:35 ` Martin Jansa
2015-08-31 19:50 ` Andre McCurdy
2015-08-31 19:38 ` Andreas Müller
2015-08-31 20:02 ` Andre McCurdy
2015-09-01 6:36 ` Anders Darander
2015-09-01 21:57 ` Andre McCurdy
2015-09-01 22:07 ` Martin Jansa
2015-09-02 0:00 ` Khem Raj
2015-09-02 0:07 ` Andre McCurdy
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=559BDA5C.6060905@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.