From: Roy Marples <uberlord@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] elibtoolize and when to drop it from an ebuild
Date: Wed, 17 Oct 2007 15:54:36 +0100 [thread overview]
Message-ID: <1192632876.2388.18.camel@uberlaptop.development.ltl> (raw)
Hello List
The BSD team is starting to get a touch irritated by the constant
dropping of elibtoolize from ebuilds. We need this so that we get
nice .so version numbers as well as to fix a few libtool issues on the
BSD platforms.
Just because it's there doesn't mean it's safe to remove as it changes
nothing on your Linux box. But that's OK as I've been adding them back
when I find it dropped with a nice comment about the issue.
I do however take objection when the command AND the comment is removed.
Please stop this as you piss off our users who have to revdep-rebuild
needlessly.
Basically, if it has a fbsd keyword don't drop elibtoolize without
querying us first.
Thanks
Roy
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2007-10-17 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 14:54 Roy Marples [this message]
2007-10-17 19:51 ` [gentoo-dev] Re: elibtoolize and when to drop it from an ebuild 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
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=1192632876.2388.18.camel@uberlaptop.development.ltl \
--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