From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: elibtoolize and when to drop it from an ebuild
Date: Wed, 17 Oct 2007 15:25:30 -0700 [thread overview]
Message-ID: <20071017222530.GB5699@supernova> (raw)
In-Reply-To: <pan.2007.10.17.19.51.54@cox.net>
On 19:51 Wed 17 Oct , Duncan wrote:
> What about putting it in an fbsd conditional? That way Linux users don't
> have to deal with the step if it's unnecessary for them, while the fbsd
> users still get it when they need it. Seems to me this should be a
> workable compromise, where people might otherwise be inclined to remove
> it.
I prefer to avoid conditionals wherever reasonable, because then you
just have more code paths to test.
Thanks,
Donnie
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-17 22:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 14:54 [gentoo-dev] elibtoolize and when to drop it from an ebuild Roy Marples
2007-10-17 19:51 ` [gentoo-dev] " Duncan
2007-10-17 22:25 ` Donnie Berkholz [this message]
2007-10-17 22:59 ` Roy Marples
2007-10-17 23:08 ` Petteri Räty
2007-10-17 23:19 ` Roy Marples
2007-10-29 11:56 ` Mike Frysinger
2007-10-29 11:54 ` Mike Frysinger
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=20071017222530.GB5699@supernova \
--to=dberkholz@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