David:
Hey, thanks for the script idea. I'll try that:
> GLIBC_VERSION=$(basename /lib/libc-*.so .so)
> GLIBC_VERSION=${GLIBC_VERSION##*-}
>
> ...or better yet, follow that with:
>
> GLIBC_MAJOR_VERSION=${GLIBC_VERSION%%.?}
Regarding the GPL, you make a good point. Not only can
GPL'd code not be combined (and then released) with non-open code,
it can only be combined (and then released) with *any* other code
if that code itself inherits the GPL license. Many other "GPL
compatible" open-source licenses, such as the Sleepycat license,
don't specify *which* license the new source code must be released
under, only that it must be open-source.
Again...I'm playing fast & loose with the word "combine"
up there. The GPL FAQ (www.gnu.org/licenses/gpl-faq.html) dedicates
more than a few lines to "what is the difference between mere
aggregation and combinining two modules into one program",
addressing details as low-level as the means one portion invokes
the other (fork, exec, pipes, rpc) and the semantics of the
communication.
Which, I don't believe, has hit the courts yet. It's
a question of legality that will eventually be presented to
judge. And that'll be an interesting event...
-Scott
> > Here's how I keep them straight: there are basically
> > two things an open-source license speaks towards: can the code
> > be combined with non-open code; can modifications be taken
> > private into closed apps. The GPL says no to both. The LGPL
> > says yes to the first, no to the second. The BSD license says
> > yes to both.
> > Playing fast and loose here, but AFAIK that's a good
> > rule of thumb(s).
>
> Of course, there are MORE things than that. One of the most important:
> GPL is "viral" in that any code that uses GPL-licensed code MUST be GPL
> licensed; BSD licenses don't have that. The X Consortium caused quite a
> stir when they tried to take X into the commercial realm as a
> proprietary private product - which they could do under their license.
> Under a GPL license, they couldn't do that.
>
> _______________________________________________
> Leaf-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/leaf-devel
>
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
