public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Seemant Kulleen <seemant@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] putting apache / apache2 on 'need' line
Date: Mon, 1 Sep 2003 19:49:08 -0700	[thread overview]
Message-ID: <20030901194908.01259cf6.seemant@gentoo.org> (raw)
In-Reply-To: <0965EC92EF999641B60A596DF3A331DF0145DCF6@wfmail01.intranet.veridian.com>

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

On Mon, 1 Sep 2003 11:55:34 -0400 
"Martin, Stephen" <stephen.martin@veridian.com> wrote:

> Hi all,
> I'm finishing up an ebuild that starts a daemon and depends on apache.
>  The
> problem is that it can use either apache or apache2.  How do I handle
> this in the need line of the init script, since apache and apache2
> have separate flags?  I'm thinking I need to do something like 'need
> apache || apache2'. What's the correct way to handle this?  Or should
> I just say it depends on apache2 and be done with it?

Azarah can better advise you, but I should think the apache initscripts
should just provide a virtual/apache and then your script can just "need
apache" or some such.  Az, Donny, Robin?

-- 
Seemant Kulleen
Developer and Project Co-ordinator,
Gentoo Linux					http://dev.gentoo.org/~seemant

Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x3458780E
Key fingerprint = 23A9 7CB5 9BBB 4F8D 549B 6593 EDA2 65D8 3458 780E

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

  parent reply	other threads:[~2003-09-02  2:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-01 15:55 [gentoo-dev] putting apache / apache2 on 'need' line Martin, Stephen
2003-09-02  2:41 ` Jacob Smullyan
2003-09-02 17:39   ` Martin, Stephen
2003-09-02  2:49 ` Seemant Kulleen [this message]
2003-09-02 17:22   ` Martin, Stephen

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=20030901194908.01259cf6.seemant@gentoo.org \
    --to=seemant@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