From: "Duncan" <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Re: Changes to the way Java packages are built
Date: Mon, 19 Jun 2006 16:48:40 +0000 (UTC) [thread overview]
Message-ID: <e76kh8$7mu$1@sea.gmane.org> (raw)
In-Reply-To: 44958E4A.6010000@gentoo.org
Alec Warner <antarus@gentoo.org> posted 44958E4A.6010000@gentoo.org,
excerpted below, on Sun, 18 Jun 2006 13:32:58 -0400:
> May I ask, because I'm very confused, wtf is freedomware?
>
> I can only assume you mean oss/free java?
As distinct from "freeware", and also known as Free or Libre Software,
libre being translated free as in freedom (where freeware in common usage
means free as in beer, or sometimes free as in deliberately public domain,
neither one of which is appropriate here), thus libre software ==
libreware == freedomware (and as opposed to slaveryware aka
another-is-your-master-ware, xref the sig).
Some here don't care. That's fine -- for them. It's a bit bigger
than that for me, but they don't ask me to run what is to me slaveryware,
and I won't ask them to give up what is to them "convenienceware".
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-19 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 15:39 [gentoo-dev] Changes to the way Java packages are built Joshua Nichols
2006-06-18 16:51 ` [gentoo-dev] " Duncan
2006-06-18 17:32 ` Alec Warner
2006-06-19 16:48 ` Duncan [this message]
2006-06-19 18:35 ` [gentoo-dev] " Bob Young
2006-06-18 17:46 ` [gentoo-dev] " Joshua Nichols
2006-06-19 16:14 ` [gentoo-dev] " Duncan
2006-06-18 19:13 ` [gentoo-dev] " Francesco Riosa
2006-06-19 7:45 ` Kevin F. Quinn
2006-06-19 11:31 ` Joshua Nichols
2006-06-20 0:09 ` Joshua Nichols
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='e76kh8$7mu$1@sea.gmane.org' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@lists.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