From: Spider <spider@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] reason for dhcpcd in system profile ?
Date: Sun, 24 Aug 2003 22:40:16 +0200 [thread overview]
Message-ID: <20030824224016.235193af.spider@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]
ok, this breaks threading but I just got a bounce due to wrong sender
address, (having mailprobs)
---
begin quote
On Sun, 24 Aug 2003 20:16:07 +0200
Paul de Vrieze <pauldv@gentoo.org> wrote:
> On Sunday 24 August 2003 18:44, Spider wrote:
> > begin quote
> > On Sun, 24 Aug 2003 11:32:22 -0500
>
> > > lpr
> >
> > But, Am I the only one who sees an advantage in moving the default
> > profiles to LSB compliance, and providing an alternated "light" one
> > for the cases that want them? (heck, if you dislike dhcpcd I'm
> > pretty sure you don't want the bloat of glibc either, go for uclibc.
> > ;) but sarcasm
> > aside, the suggestion is serious.
>
> Well, I can see the advantage of mimmicing the LSB, but for example
> lpr does not make sense without a printer, and setting up a printer
> takes configuring anyway so I don't feel it should be part of system
Here we can disagree, as the LSB defines lpr, it can well be just an
offline printer (print-to-file setup) which can very well be configured
per default.
However, if we wish to include it in the basic profile or not is another
question. I still think that doing so (or posix compliance, see thread
about bloat.) could provide to be a benefit for the project.
//Spider
--
begin .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-08-24 20:40 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-24 20:40 Spider [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-23 19:04 [gentoo-dev] reason for dhcpcd in system profile ? Marius Mauch
2003-08-23 19:20 ` Wolfram Schlich
2003-08-23 20:23 ` Daniel Armyr
2003-08-23 21:20 ` Wolfram Schlich
2003-08-24 6:08 ` Daniel Armyr
2003-08-23 23:06 ` Luke-Jr
2003-08-24 3:21 ` A. Craig West
2003-08-24 8:59 ` Spider
2003-08-24 16:32 ` Alec Berryman
2003-08-24 16:44 ` Spider
2003-08-24 18:16 ` Paul de Vrieze
2003-08-24 18:40 ` Alec Berryman
2003-08-24 18:55 ` Andrew Gaffney
2003-08-24 18:47 ` Paul de Vrieze
2003-08-24 19:05 ` Andrew Gaffney
2003-08-24 19:03 ` Marius Mauch
2003-08-25 0:44 ` Andrew Gaffney
2003-08-25 0:48 ` Andrew Gaffney
2003-08-24 22:00 ` Grant Goodyear
2003-08-25 3:07 ` Luke-Jr
2003-08-23 19:29 ` Stewart Honsberger
2003-08-23 20:29 ` Kevyn Shortell
2003-08-24 7:22 ` Stewart Honsberger
2003-08-24 8:33 ` Kevyn Shortell
2003-08-24 15:09 ` Brad Laue
2003-08-24 20:41 ` Kevyn Shortell
2003-08-23 21:25 ` Norberto BENSA
2003-08-23 20:34 ` Yuri Enshin
2003-08-23 21:27 ` Norberto BENSA
2003-08-23 23:16 ` Luke-Jr
2003-08-24 8:15 ` Martin Schlemmer
2003-08-25 2:18 ` Luke-Jr
2003-08-25 4:24 ` Martin Schlemmer
2003-08-25 4:46 ` Martin Schlemmer
2003-08-25 13:46 ` Luke-Jr
2003-08-25 16:27 ` William Hubbs
2003-08-23 23:08 ` Lloyd D Budd
2003-08-24 4:28 ` Andrew Gaffney
2003-08-24 14:14 ` Marius Mauch
2003-08-24 14:33 ` Martin Schlemmer
2003-08-24 15:09 ` Paul de Vrieze
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=20030824224016.235193af.spider@gentoo.org \
--to=spider@gentoo.org \
--cc=gentoo-dev@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