public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: elibtoolize and when to drop it from an	ebuild
Date: Thu, 18 Oct 2007 02:08:37 +0300	[thread overview]
Message-ID: <471695F5.1080001@gentoo.org> (raw)
In-Reply-To: <1192661981.2783.38.camel@uberpc.marples.name>

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

Roy Marples kirjoitti:
> On Wed, 2007-10-17 at 15:25 -0700, Donnie Berkholz wrote:
>> 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.
> 
> What's more, elibtoolize does more than just fix any FreeBSD issues as
> it fixes stuff for uclibc and darwin based platforms. It also fixes some
> old crusty libtools in packages that affect Linux/glibc installs too.
> 
> So just because you don't need it, doesn't mean that someone else
> doesn't either.
> 
> Thanks
> 
> Roy
> 

I don't pretend to know much about elibtoolize but if it's so useful why
 it's not needed to always run it?

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2007-10-17 23:21 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
2007-10-17 22:59     ` Roy Marples
2007-10-17 23:08       ` Petteri Räty [this message]
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=471695F5.1080001@gentoo.org \
    --to=betelgeuse@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