On 27 Wrz, 01:14, Paul Lindner <[email protected]> wrote:
> I wrote the memcached sysv script and adapted it to fit fedora norms.  No
> worries there regarding license.

So, it's covered by Memcached license or that MIT license I
mentioned ?


>
> 2010/9/25 dormando <[email protected]>
>
>
>
>
>
> > Uhhhm.
>
> > memcached-init is from:
>
> > commit 4b1b1ae76ef6e78dd3f1d753931ac8051ae99e9a
> > Author: Brad Fitzpatrick <[email protected]>
> > Date:   Tue Dec 30 19:56:33 2003 +0000
>
> > I assume brad copied the skeleton files and modified it. IANAL so I'm not
> > sure how much of it had to be changed to be able to flip the license, but
> > it seems like a trivial script.
>
> > The sysv one is from:
>
> > commit 275f8c40705526ac4514d5dcff2cbf0311b540ac
> > Author: Paul Lindner <[email protected]>
> > Date:   Fri May 4 11:23:02 2007 +0000
>
> >    add rpm spec file, new sysv init script
>
> > So uh. Paul? Care to comment?
>
> > and finally, may I ask why you're finding this issue? Do you work for a
> > distro or are just curious? Or you're trying to package it up and sell it?
> > :P
>
> > On Tue, 21 Sep 2010, Tomasz Zieliński wrote:
>
> > > Hello,
>
> > > I've noticed that the two scripts mentioned in the subject are
> > > probably taken from some external
> > > sources and licensed under different licenses than Memcached itself.
>
> > > Memcached-init clearly says that it is taken from Debian. It's similar
> > > to /etc/init.s/skeleton on my Ubuntu 9.04,
> > > which belongs to initscripts package and that package is licensed
> > > under GPL3.
> > > Not sure which license applies to the memcached-init, but I suppose
> > > it's either GPL2 or GPL3.
>
> > > Regarding memcached.sysv, I found a similar script here:
>
> >http://killersoft-yum.googlecode.com/svn-history/r24/trunk/repo/SOURC...
> > > - not sure who copied it from who, but in case killersoft-yum was
> > > first - it's licensed under MIT license (http://code.google.com/p/
> > > killersoft-yum/ ->http://www.opensource.org/licenses/mit-license.php).
>
> > > Can someone responsible for this area comment on the topic?
>
> > > --
> > > Tomasz Zielinski
>
> --
> Paul Lindner -- [email protected] -- linkedin.com/in/plindner

Reply via email to