From: Roy Marples <uberlord@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 00:19:42 +0100 [thread overview]
Message-ID: <1192663182.2783.42.camel@uberpc.marples.name> (raw)
In-Reply-To: <471695F5.1080001@gentoo.org>
On Thu, 2007-10-18 at 02:08 +0300, Petteri Räty wrote:
> I don't pretend to know much about elibtoolize but if it's so useful why
> it's not needed to always run it?
Not every package uses libtool, or other GNU autotools.
Sometimes it has to be run in specific directories instead of just the
toplevel one.
But also, consider this - if an ebuild supplies src_unpack and
src_compile how is it supposed to get called?
Thanks
Roy
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-17 23:33 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
2007-10-17 23:19 ` Roy Marples [this message]
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=1192663182.2783.42.camel@uberpc.marples.name \
--to=uberlord@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