From: "Eric Brown" <ebrown@magbank.com>
To: <gentoo-dev@lists.gentoo.org>
Subject: RE: [gentoo-dev] init script guidelines
Date: Tue, 19 Jul 2005 15:39:16 -0400 [thread overview]
Message-ID: <16CC9569DA3E4D41A1D4BC25D7B5A16A473AF7@hercules.magbank.com> (raw)
Not everyone can patch them, more people would be capable of writing
half-baked hacks that resolve most of the issues.
Anyway I guess the new baselayout sounds promising here.
> My point is that Snort and Apache are not alone in this, so I suppose
> quite a few upstream developers just disagree with us on what proper
> initialization means. Why should our users suffer?
They shouldn't, but that doesn't mean implementing some half-baked hack
to resolve the situation. It might be better to instead patch the
daemon in question and send the patches upstream. Upstream developers
(usually) are much more willing to make changes when you've done the
work for them... ;]
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2005-07-19 19:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 19:39 Eric Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-19 18:08 [gentoo-dev] init script guidelines Eric Brown
2005-07-19 18:40 ` Chris Gianelloni
2005-07-19 20:43 ` Michael Cummings
2005-07-19 21:07 ` Chris Gianelloni
2005-07-19 21:53 ` Martin Schlemmer
2005-07-20 6:30 ` Roy Marples
2005-07-19 20:03 ` Mike Frysinger
2005-07-19 16:42 Eric Brown
2005-07-19 17:22 ` Chris Gianelloni
2005-07-19 17:45 ` Mike Frysinger
2005-07-19 18:00 ` Roy Marples
2005-07-19 22:16 ` Francesco R
2005-08-23 14:09 ` Paul de Vrieze
2005-08-31 7:13 ` Roy Marples
2005-08-31 8:05 ` Roy Marples
2005-08-31 8:24 ` Georgi Georgiev
2005-08-31 17:38 ` Roy Marples
2005-07-19 18:14 ` Francesco R
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=16CC9569DA3E4D41A1D4BC25D7B5A16A473AF7@hercules.magbank.com \
--to=ebrown@magbank.com \
--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