Re: [gentoo-dev] LLVM News item

[Ian Stakenvicius]

On 25/10/16 06:44 PM, Joakim Tjernlund wrote:
> On Tue, 2016-10-25 at 16:07 -0400, Ian Stakenvicius wrote:
>> On 25/10/16 04:02 PM, Joakim Tjernlund wrote:
>>>
>>> On Tue, 2016-10-25 at 15:41 -0400, Ian Stakenvicius wrote:
>>>>
>>>> On 25/10/16 03:32 PM, Ian Stakenvicius wrote:
>>>>>
>>>>>
>>>>> On 25/10/16 03:08 PM, Joakim Tjernlund wrote:
>>>>>>
>>>>>>
>>>>>> On Tue, 2016-10-25 at 20:11 +0200, Michał Górny wrote:
>>>>>>>
>>>>>>>
>>>>>>> On Tue, 25 Oct 2016 17:32:22 +0000
>>>>>>> Joakim Tjernlund <Joakim.Tjernlund@××××××××.com> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Noticed todays 2016-10-25-llvm_3_9_with_llvm_targets news item and read:
>>>>>>>> ..
>>>>>>>> In order to enable all targets, add the following to your
>>>>>>>> /etc/portage/package.use or equivalent file:
>>>>>>>>
>>>>>>>>   sys-devel/llvm LLVM_TARGETS: *
>>>>>>>>   sys-devel/clang LLVM_TARGETS: *
>>>>>>>> ...
>>>>>>>>
>>>>>>>> I would like to control such variables(LLVM_TARGETS) through the profile as
>>>>>>>> well but it seems not supported?
>>>>>>>
>>>>>>> Why not? We're already setting the defaults in profiles, and you can do
>>>>>>> whatever you want in your own profile. The news item is focused on
>>>>>>> regular users, so it covers the usual configuration files rather than
>>>>>>> creating custom profiles.
>>>>>>>
>>>>>>
>>>>>> How? in my profile(which inherits gentoo:default/linux/amd64/13.0/desktop) I just tested to add:
>>>>>> # > svn diff
>>>>>> Index: package.use
>>>>>> ===================================================================
>>>>>> --- package.use	(revision 1087)
>>>>>> +++ package.use	(working copy)
>>>>>> @@ -1,3 +1,6 @@
>>>>>> +sys-devel/llvm LLVM_TARGETS: *
>>>>>> +sys-devel/clang LLVM_TARGETS: *
>>>>>>
>>>>>> Then I get:
>>>>>> # > emerge -aNDuv world
>>>>>> --- Invalid USE flag for 'sys-devel/llvm' in
>>>>>> '/var/lib/layman/transmode/profiles/gentoo64/package.use':
>>>>>> 'LLVM_TARGETS:'
>>>>>> --- Invalid USE flag for 'sys-devel/llvm' in
>>>>>> '/var/lib/layman/transmode/profiles/gentoo64/package.use':
>>>>>> '*'
>>>>>> --- Invalid USE flag for 'sys-devel/clang' in
>>>>>> '/var/lib/layman/transmode/profiles/gentoo64/package.use':
>>>>>> 'LLVM_TARGETS:'
>>>>>> --- Invalid USE flag for 'sys-devel/clang' in
>>>>>> '/var/lib/layman/transmode/profiles/gentoo64/package.use':
>>>>>> '*'
>>>>>>
>>>>>
>>>>> Syntax error:
>>>>>
>>>>> sys-devel/llvm llvm_targets_firstone llvm_targets_secondone ..
>>>>> sys-devel/clang llvm_targets_firstone llvm_targets_secondone ..
>>>
>>> This is standard USE flags, not the VAR: x y z syntax
>>>
>>>>
>>>>>
>>>>>
>>>>>
>>>>> You can't specify wildcards to enable groups of use flags.
>>>>>
>>>>>
>>>>
>>>> Correction, the earlier syntax *is* supposed to work (and tested that
>>>> it works here, with VIDEO_CARDS)..  If I had to guess this probably
>>>> relates to an issue with the transmode overlay.
>>>>
>>>
>>> Hmm, are you saying that you can write:
>>>   x11-base/xorg-drivers VIDEO_CARDS: intel radeon
>>> in your profile?
>>>
>>> Any idea what my issue might be?
>>>
>>>  Jocke
>>>
>>
>> In my profile as in /etc/portage/package.use/  , yes. Specifically I
>> tested VIDEO_CARDS: *
>
> I thought it was obvious that I was referring to a custom profile
> as in eselect profile ..
>
>>
>> I *didn't* try to mess with my in-repo profile though.  Given that
>> repositories may well need to follow PMS, and the USE_EXPAND: * syntax
>> is a portage'ism, this is why they are being rejected in the
>> transmode-overlay case.  I certainly can't find an example of this
>> syntax in the gentoo repo.
>
> Portage supports lots more than PMS as is, should we remove that?
> Just because something is supported in portage, you don't have to use it
> in official repos. Our overlay is used to maintain all the linux computers
> we have here and /etc/portage is the individual using a particular computer.
>
> It would be nice if portage, in general, supported the same features/syntax as
> /etc/portage does.
>
>   Jocke
>

In-repo profiles are subject to the Package Manager Specification
(PMS), so portage'isms are supposed to be avoided.  Package managers
can have pretty much whatever extensions they want in terms of extra
syntax, etc. in their configuration files/settings though, which is
why this syntax is fine in /etc/portage.