From: Joshua Brindle<method@gentoo.org>
To: gentoo-dev@gentoo.org, "Ludd, Ned"<solar@gentoo.org>
Subject: Re: [gentoo-dev] apache.eclass proposed
Date: 8 Jun 2003 09:32:00 -0500 [thread overview]
Message-ID: <20030608T093241Z_B95E00150000@gentoo.org> (raw)
This is very good, I've seen many apache related ebuilds that do
not do the right thing about determining what apache/which configs
which directories, etc to use, I think that all apache related ebuilds
should use this, it's an easy and central way to manage the logic
of apache configs
Good job solar :)
>After writing a net-www/ ebuild it seemed apparent to me that we are
>going to need an apache.eclass. A quick find in portage reveals quite a
>few independent ebuilds all needing the basic functionality that could
>be provided by an apache.eclass
>
>syntactically perfect the idea is what matters..
>I have attached an apache.eclass that I welcome your input/feedback on.
>While it may not be syntactically perfect for the apache2 part its the
>idea that we get this out there and start talking about one that
>matters.
>
>my portage # find . -name '*.ebuild' | xargs grep HTTPD_USER= | wc
> 22 96 1904
>my portage # find . -name '*.ebuild' | xargs grep HTTPD_GROUP= | wc
> 21 123 2081
>my portage # find . -name '*.ebuild' | xargs grep HTTPD_ROOT= | wc
> 50 299 5154
>--
>Ned Ludd <solar@gentoo.org>
>Gentoo Linux (Hardened)
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-06-08 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-08 14:32 Joshua Brindle [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-08 10:12 [gentoo-dev] apache.eclass proposed Ned Ludd
2003-06-08 19:45 ` Robin H.Johnson
2003-06-08 19:50 ` Paul de Vrieze
2003-06-09 3:07 ` Ned Ludd
2003-06-09 6:01 ` Robin H.Johnson
2003-06-09 17:23 ` Brad Laue
2003-06-10 3:02 ` Donny Davies
2003-06-10 5:43 ` Robin H.Johnson
2003-06-12 0:13 ` Stewart
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=20030608T093241Z_B95E00150000@gentoo.org \
--to=method@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=solar@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