public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: srbaker@mysterymachine.ddts.net (Steven R. Baker)
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Distribution Name
Date: Mon Jan 29 22:43:01 2001	[thread overview]
Message-ID: <87itmxlhmr.fsf@scooby.mysterymachine.ddts.net> (raw)
In-Reply-To: Jerry A!'s message of "Tue, 30 Jan 2001 00:37:20 -0500"

	I can't speak for Dan, but...  Isn't GNU/Linux a Stallmanism?
	I recall reading an interview with Linus where he doesn't even
	think it should be called GNU/Linux, but just plain Linux.

Yes, GNU/Linux *is* a Stallmanism, it just so happens that Stallman is
right and Linus is wrong.  Linux is just a kernel, nothing more.  An
operating system consists of a kernel as well as the software that
goes into it.  The software that makes up a base system is made by GNU
(the compiler, libc, all of the userland utilities) therefore, it's a
GNU system.  You can be running a BSD, Sun, Mach, or HURD kernel and
still be running a GNU system.

Some argue that FreeBSD uses GCC and other GNU utilities as well,
however, FreeBSD uses *only* the GNU C Compiler, and has their own
libc and userland utilities.  GNU/Linux is the correct name for a GNU
system running on top of the Linux kernel.

	However, the license is OSI-compliant.  In theory, this code
	"infection" would take place if we were talking about GPL/BSD
	projects.

	Though, I don't see this as an issue.  We're not developing or
	extending the internals of Python.  Everything is being
	created as external packages.

Is Python in Gentoo linked with libreadline?  If so, that's a GPL
violation.  Don't get me wrong, I *love* Python, but there should be
some sort of policy or mechanism that says what can go in to Gentoo
and what can't.  Don't you care about your Freedom?



  reply	other threads:[~2001-01-30  5:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-29 22:19 [gentoo-dev] Distribution Name Steven R. Baker
2001-01-29 22:37 ` Jerry A!
2001-01-29 22:43   ` Steven R. Baker [this message]
2001-01-29 23:24     ` Jerry A!
2001-01-30  0:06       ` Steven R. Baker
2001-02-01 12:03         ` Bill Anderson
2001-02-01 13:31           ` drobbins
2001-01-30 11:51     ` drobbins
2001-01-30 15:02       ` Aaron Held
2001-01-30 15:24         ` Jerry A!
2001-01-30 15:42           ` Aaron Held
2001-01-30 19:46         ` Steven R. Baker
2001-02-01 11:38           ` Bill Anderson
     [not found]       ` <drobbins@gentoo.org>
2001-01-30 19:38         ` Steven R. Baker
2001-01-30  5:22 ` Achim Gottinger
2001-02-01 11:34 ` Bill Anderson
2001-02-01 11:53   ` Achim Gottinger
2001-02-01 18:33     ` Bill Anderson

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=87itmxlhmr.fsf@scooby.mysterymachine.ddts.net \
    --to=srbaker@mysterymachine.ddts.net \
    --cc=gentoo-dev@gentoo.org \
    /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