public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stuart Herbert <stuart@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] net-www Being Retired
Date: Wed, 15 Sep 2004 23:30:16 +0100	[thread overview]
Message-ID: <200409152330.20092.stuart@gentoo.org> (raw)
In-Reply-To: <4148AAB5.6090300@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1841 bytes --]

Hi Doug,

On Wednesday 15 September 2004 21:48, Doug Goldstein wrote:
> I'm actually the maintainer of a couple of Apache modules (currently not
> included in Portage but shortly I'll look to include them when I
> stablize them a bit more) that I have the codebase support both Apache 1
> and Apache 2 through a mess of #DEFINE and ./configure but I did that to
> make it easier for users. 

Please make sure you add yourself to the apache herd when you commit these 
modules, and that you list yourself as primary maintainer in the 
metadata.xml.

> With this scheme the package would have to 
> appear in two catagories under the same name and it would conflict with
> the other one and provide an ugly mess. 

Yes, the package would have to appear in two categories.  The common parts of 
the ebuild can be moved into an eclass.  I'm not sure what conflict you think 
will arise.  All mods that support both apache1 and apache2 should install 
into SLOT=1 for apache1 and SLOT=2 for apache2.

> Heck.... every package... like 
> emerge mod_perl wouldn't even work.. it'd give you an ugly message
> saying which one? www-apache1/mod-perl or www-apache2/mod-perl... Not
> ideal in my book. There's got to be a better way about this.

You'd only get that message if you typed 'emerge mod_perl'.  If you typed 
'emerge www-apache1/mod_perl', then you wouldn't get the message.

As I say, I'm open to suggestions.

Best regards,
Stu
-- 
Stuart Herbert                                              stuart@gentoo.org
Gentoo Developer                                       http://www.gentoo.org/
                                                   http://stu.gnqs.org/diary/

GnuPG key id# F9AFC57C available from http://pgp.mit.edu
Key fingerprint = 31FB 50D4 1F88 E227 F319  C549 0C2F 80BA F9AF C57C
--

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-09-15 22:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-19 13:06 [gentoo-dev] net-www Being Retired Stuart Herbert
2004-07-19 13:32 ` Georgi Georgiev
2004-07-19 20:49   ` Stuart Herbert
2004-07-19 16:56 ` Sergey Borodich
2004-07-19 20:53   ` Stuart Herbert
2004-09-15 19:48 ` Stuart Herbert
2004-09-15 20:10   ` Donnie Berkholz
2004-09-15 20:22     ` Stuart Herbert
2004-09-15 20:48       ` Doug Goldstein
2004-09-15 22:14         ` Allen Parker
2004-09-15 22:30         ` Stuart Herbert [this message]
2004-09-16  0:02           ` Jason Rhinelander
2004-09-16  0:09             ` Michael Tindal
2004-09-16  8:02           ` Paul de Vrieze
2004-09-16 10:43     ` Michiel de Bruijne

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=200409152330.20092.stuart@gentoo.org \
    --to=stuart@gentoo.org \
    --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