I would very much prefer that the GPLv2 license of screen be
maintained. What do I need to do to keep a GPLv2 license on
it ?
(Sorry for taking so long to respond to this, but I didn't see the
initial thread.)
Enjoy!
-- radzy
________________________________________
From: Randy MacLeod [randy.macl...@windriver.com]
Sent: Thursday, August 20, 2015 8:37 AM
To: Radzykewycz, T (Radzy)
Subject: Re: [OE-core] [PATCHv2 1/1] screen: Upgrade 4.0.3 -> 4.3.1
On 19 August 2015 at 09:17, Jussi Kukkonen
<jussi.kukko...@intel.com<mailto:jussi.kukko...@intel.com>> wrote:
>> * License is now GPLv3+
>
> What about GPLv2 version which was preserved (IIRC) in prevous patch?
>
> Why did you decide to drop it now?
Mostly because of Ross' comment "Is screen considered sufficiently
core that we should maintain both GPLv2 and v3 recipes? I'm not
convinced it is".
I did try to coax people to explain their thoughts in a little more
detail (because I wasn't sure what exactly they were saying) in my
reply on Aug 12 but no-one did... So I figured it's better to talk
with patches: I believe maintaining the GPLv2 version is not a great
use of anyones time (and I think it's fair to say that the recipe
wasn't receiving the sort of attention it would have required) and
making a developer tool like that GPLv3 shouldn't be a problem to most
people.
FWIW, I still agree with my statement and with Jussi here.
Ross
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
