From: Luke-Jr <luke-jr@gentoo.org>
To: dams@idm.fr, Caleb Tennis <caleb@gentoo.org>
Cc: Stanislav Brabec <utx@penguin.cz>,
aeriksson@fastmail.fm, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] gentoo vs. the FHS
Date: Tue, 23 Sep 2003 23:11:53 +0000 [thread overview]
Message-ID: <200309232312.05766.luke-jr@gentoo.org> (raw)
In-Reply-To: <m24qz3duhy.fsf@krotkine.idm.fr>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 23 September 2003 10:12 pm, dams@idm.fr wrote:
> FHS is made so that f*cking proprietary application get well installed on
> every distribution, so that they can sell more, and make the big linux
> actors (IBM and co), more rich.
Proprietary applications should not exist in the first place, AFAIC. If this
is the purpose of the FHS, then I'm all for non-compliance! :)
>
> If you agree with this way to let linux go forward (I have no opinion on
> that), then be FHS compliant. It's certain that being FHS compliant is a
> plus when dealing with proprietary software companies.
Would we want proprietary software companies to maintain their own ebuilds in
the portage tree anyway? I'd consider many open source project developers
better qualified for that before a proprietary developer. Therefore, seeing
as all the proprietary ebuilds are likely to be maintained outside of the
company creating them anyway, do we need to deal with them at all (except in
crazy EULA cases like Id, of course)?
- --
Luke-Jr
Developer, Gentoo Linux
http://www.gentoo.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/cNNBZl/BHdU+lYMRAnFyAJ9TXlhxdscZJtBNvvanzdSg5+X8hQCeN5/r
xrnOZ5QH2FjdMHwZ7mOzwI0=
=l1FW
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-09-23 23:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 6:32 [gentoo-dev] gentoo vs. the FHS aeriksson
2003-09-23 20:08 ` Stanislav Brabec
2003-09-23 20:26 ` Matt Chorman
2003-09-23 20:58 ` Caleb Tennis
2003-09-23 22:12 ` dams
2003-09-23 23:11 ` Luke-Jr [this message]
2003-09-24 0:21 ` William Kenworthy
2003-09-24 3:33 ` Daniel Robbins
2003-09-24 7:18 ` Sven Vermeulen
2003-09-24 1:08 ` Kevin Lacquement
2003-09-24 7:20 ` Sven Vermeulen
2003-09-24 3:32 ` Daniel Robbins
2003-09-23 21:26 ` Paul de Vrieze
2003-09-24 14:21 ` splite-gentoo
2003-09-24 18:10 ` Stanislav Brabec
2003-09-24 2:37 ` Mike Frysinger
2003-09-24 3:35 ` Daniel Robbins
2003-09-29 3:47 ` Mike Frysinger
2003-09-29 15:18 ` Luke-Jr
2003-09-30 12:59 ` Stuart Herbert
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=200309232312.05766.luke-jr@gentoo.org \
--to=luke-jr@gentoo.org \
--cc=aeriksson@fastmail.fm \
--cc=caleb@gentoo.org \
--cc=dams@idm.fr \
--cc=gentoo-dev@gentoo.org \
--cc=utx@penguin.cz \
/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