public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dan Armak <ermak@netvision.net.il>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Linux Standard Base
Date: Mon Jul  9 11:49:02 2001	[thread overview]
Message-ID: <01070920485302.00654@localhost> (raw)
In-Reply-To: <000401c10896$378a1f40$6669a8c0@ortega-lt.hsdrs.com>

On Monday 09 July 2001 19:43, you wrote:
> I was reading in LinuxToday some comments about the LSB and just about
> everyone is singing praises to it.
>
> You may get the specs at
>
> http://www.linuxbase.org/spec/
>
> There are a couple of topics there that would be of concern for Gentoo. One
> is the topic of packaging. Packaging addresses binaries and states that RPM
> is to be supported. The other is system Init.
>
> The pages in the specs (PDF format) are not numbered. The section on
> packaging start in page 229 (chapter 13) and the one on system init on page
> 352 (Chapter 18). I got there using the thumbnails. This is a long
> document, almost 400 pages.
>
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@cvs.gentoo.org
> http://cvs.gentoo.org/mailman/listinfo/gentoo-dev


With all due respect to LSB, I really don't think RPM is a Good Thing. At 
all. Actually RPM as it exists now doesn't provide the features needed to use 
it everywhere. Not only Gentoo but Slackware, Debian, etc.... don't support 
RPM - at least not as their main, preferred way of packaging.

The whole point of having many contending distros around is for differences - 
customization being an issue.

The LSB wants things to be _standard_. This means programs working 
out-of-the-box. In this case, distributed packages working on all 
distributions.

But there's already one such method that always works - configure; make; make 
install. If LSB says RPMs are better than that, it discourages practicing 
what is the heart of Portage - automatized downloading, compiling & 
installing. The LSB should push for standardized results, not for a standard 
way of achieving them.

Whoever wants a pre-compiled package will eventually be able to get it via 
Portage which already supports binary packages. Whoever gets a package from 
its home site as source is thus encouraged to write an ebuild for it and give 
back to the community. RPM availability would desatroy that - Portage and 
emerge would simply become much less important. 

Of course, choice is important. So whoever thinks RPMs are good for Gentoo 
can go ahead and modify Portage/emerge to support them. But people who still 
think actually compiling a package with the correct optimizations for you CPU 
is best <gasp> shouldn't be branded non-standard. (Or non-mainstream <gasp>).

Well, that's my opinion, for what it's worth. (phew!)

Dan Armak



  reply	other threads:[~2001-07-09 17:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-09 10:37 [gentoo-dev] Linux Standard Base Luis Ortega
2001-07-09 11:49 ` Dan Armak [this message]
2001-07-09 13:26   ` Terje Kvernes
2001-07-09 23:56     ` Dan Armak
2001-07-10  0:11       ` Daniel Robbins
2001-07-10  0:21         ` Jerry A!
2001-07-10  5:29         ` Dan Armak
2001-07-10 10:53           ` Daniel Robbins
2001-07-10 13:21             ` tadpol
2001-07-09 13:57   ` Daniel Robbins
2001-07-09 23:56     ` Dan Armak
2001-07-10  0:01       ` Daniel Robbins
2001-07-10  4:39         ` Dan Armak

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=01070920485302.00654@localhost \
    --to=ermak@netvision.net.il \
    --cc=gentoo-dev@cvs.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