Petteri Räty wrote:
> Marius Mauch kirjoitti:
>
>> On Mon, 23 Apr 2007 23:45:48 +0200
>> dju` <[EMAIL PROTECTED]> 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?
>
> [EMAIL PROTECTED] /usr/portage/eclass $ grep built_with_use_die -r .
> [EMAIL PROTECTED] /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.
--
[EMAIL PROTECTED] mailing list
