From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo could become certified for IBM Server Hardware
Date: Thu, 5 May 2005 00:14:15 +0100 [thread overview]
Message-ID: <20050505001415.39e44e97@snowdrop> (raw)
In-Reply-To: <1115245904.4665.23.camel@enterprise>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
On Wed, 04 May 2005 17:31:44 -0500 David Krider <david@davidkrider.com>
wrote:
| On Wed, 2005-05-04 at 17:26 +0100, Ciaran McCreesh wrote:
| > On Wed, 4 May 2005 18:17:53 +0200 Michiel de Bruijne
| > <m.debruijne@hccnet.nl> wrote:
| > | Second showstopper is lack of (LSB-)certification;
| > | Like it or not, the typical managers in this world say if product
| > | x isn't y-certified we wont use/support it. Gentoo needs a
| > | profile for a LSB-compliant system.
| >
| > Don't be silly.
|
| Forgive me to come into a list where I should probably just be
| lurking, but this is really what I subscribed to the list for: why is
| this idea silly?
For us to support LSB:
* We'd have to use RPM instead of portage
* We'd have to support all the daft FHS ideas like /media, /srv and
/wedonotunderstandtheunixfs
* We'd have to make X support mandatory
* We'd have to ship ancient versions of core libraries
In fact, basically, we'd have to become RedHat.
--
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron)
Mail : ciaranm at gentoo.org
Web : http://dev.gentoo.org/~ciaranm
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-04 23:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 9:03 [gentoo-dev] Gentoo could become certified for IBM Server Hardware daniel.kerwin
2005-05-04 9:09 ` Donnie Berkholz
2005-05-04 9:17 ` Antwort: " daniel.kerwin
2005-05-04 10:21 ` José Alberto Suárez López
2005-05-04 10:37 ` [gentoo-dev] Re: Antwort: " Duncan
2005-05-04 10:15 ` [gentoo-dev] " Michael Cummings
2005-05-04 10:32 ` Fernando J. Pereda
2005-05-04 10:36 ` Antwort: " daniel.kerwin
2005-05-04 13:32 ` Omkhar Arasaratnam
2005-05-04 13:50 ` M. Edward (Ed) Borasky
2005-05-04 14:08 ` Omkhar Arasaratnam
2005-05-04 14:24 ` Michael Cummings
2005-05-04 14:18 ` Brett Curtis
2005-05-04 14:39 ` M. Edward (Ed) Borasky
2005-05-04 15:36 ` Brett Curtis
2005-05-04 14:12 ` Antwort: " daniel.kerwin
2005-05-04 14:28 ` Omkhar Arasaratnam
2005-05-04 14:35 ` M. Edward (Ed) Borasky
2005-05-04 13:47 ` Daniel Ostrow
2005-05-04 14:09 ` Mike Frysinger
2005-05-04 16:17 ` Michiel de Bruijne
2005-05-04 16:26 ` Ciaran McCreesh
2005-05-04 16:46 ` Lance Albertson
2005-05-04 16:55 ` Ciaran McCreesh
2005-05-04 20:28 ` Ryan
2005-05-04 22:31 ` David Krider
2005-05-04 23:14 ` Ciaran McCreesh [this message]
2005-05-05 1:28 ` Michiel de Bruijne
2005-05-05 14:11 ` Ciaran McCreesh
2005-05-09 20:27 ` Paul de Vrieze
2005-05-05 1:33 ` Chris Gianelloni
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=20050505001415.39e44e97@snowdrop \
--to=ciaranm@gentoo.org \
--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