public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michiel de Bruijne <m.debruijne@hccnet.nl>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo could become certified for IBM Server Hardware
Date: Thu, 5 May 2005 03:28:06 +0200	[thread overview]
Message-ID: <200505050328.06938.m.debruijne@hccnet.nl> (raw)
In-Reply-To: <20050505001415.39e44e97@snowdrop>

On Thursday 05 May 2005 01:14, Ciaran McCreesh wrote:
> For us to support LSB:
>
> * We'd have to use RPM instead of portage

That's not correct, quote from LSB:
"The distribution itself may use a different packaging format for its own 
packages, and of course it may use any available mechanism for installing the 
LSB-conformant packages." 

So basically we can continue to do rpm2targz like we do now and still be 
LSB-compliant.

> * We'd have to support all the daft FHS ideas like /media, /srv and
> /wedonotunderstandtheunixfs

Like you said before:
"Thing is, it really isn't a problem. Data files go in $(datadir),
configuration files go in $(sysconfdir) and so on, and the build system
handles the rest. It doesn't matter what $(datadir) is actually defined
to be (unless your code really really sucks)."

With a proper build system you can install the same package in the current 
Gentoo FHS or the LSB FHS.

> * We'd have to make X support mandatory

Only in the LSB-profile, the normal profile doesn't need to have X-libs 
installed.

> * We'd have to ship ancient versions of core libraries

There is some interest in that already, see GLEP19

> In fact, basically, we'd have to become RedHat.

I don't agree. I think the Gentoo-framework is flexible enough to give us an 
_optional_ LSB-compliant system (e.g. by selecting a profile) without making 
any consessions on the current Gentoo-structure.
-- 
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-05-05  1:28 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
2005-05-05  1:28         ` Michiel de Bruijne [this message]
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=200505050328.06938.m.debruijne@hccnet.nl \
    --to=m.debruijne@hccnet.nl \
    --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