From: Doug Goldstein <cardoe@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] add built_with_use_die() to eutils.eclass ?
Date: Fri, 18 May 2007 10:06:46 -0400 [thread overview]
Message-ID: <464DB2F6.5020903@gentoo.org> (raw)
In-Reply-To: <464CC2F6.6000904@gentoo.org>
Petteri Räty wrote:
> Marius Mauch kirjoitti:
>
>> On Mon, 23 Apr 2007 23:45:48 +0200
>> dju` <dju@gentoo.org> wrote:
>>
>>
>>> eerror "Your ${package} package has been built without"
>>> eerror "${func} support, please enable the '${use_flag}' USE flag and"
>>> eerror "re-emerge ${package}."
>>> elog "You can enable this USE flag either globally in /etc/make.conf,"
>>> elog "or just for specific packages in /etc/portage/package.use."
>>> die "${package} missing ${func} support"
>>>
>> A little detail about elog: You should not use different elog functions
>> (eerror, elog, ewarn, ...) within the same message as they may appear
>> out of order in the final log (e.g. the elog lines might appear before
>> the eerror lines). This is because messages of the same loglevel and in
>> the same phase are grouped together. It's an implementation detail that
>> might be changed in future versions, but for now you'll have to live
>> with it.
>>
>> Also I don't see much use in explaining how to enable a use flag inside
>> ebuilds, at most there should be a pointer to the real documentation
>> IMO.
>>
>> Marius
>>
>
> Any updates on this?
>
> betelgeuse@pena /usr/portage/eclass $ grep built_with_use_die -r .
> betelgeuse@pena /usr/portage/eclass $
>
> I for one would use it if it existed.
>
> Regards,
> Petteri
>
>
built_with_use sys-apps/pciutils zlib && die "You need to build
sys-apps/pciutils without zlib"
WHY do we need YET another function for such a simple construct?
built_with_use is already available and very powerful.
For example, HAL does..
built_with_use --missing false sys-apps/pciutils zlib
If the USE flag is missing entirely, it'll treat it like it's disabled
because old versions didn't have the zlib USE flag and didn't gzip their
data. Some packages it might be the other way around so you can pass
true instead.
Adding built_with_use_die is utterly pointless.
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2007-05-18 14:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 21:45 [gentoo-dev] add built_with_use_die() to eutils.eclass ? dju`
2007-04-23 21:55 ` Petteri Räty
2007-04-23 22:01 ` Doug Goldstein
2007-04-23 23:09 ` Lars Weiler
2007-04-23 18:27 ` Zac Medico
2007-04-24 8:09 ` Julien Allanos (dju`)
2007-04-24 8:49 ` Marius Mauch
2007-05-17 21:02 ` Petteri Räty
2007-05-18 14:06 ` Doug Goldstein [this message]
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=464DB2F6.5020903@gentoo.org \
--to=cardoe@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