On 10/23/2015 02:21 AM, Joakim Tjernlund wrote:
> On Thu, 2015-10-22 at 11:54 -0700, Zac Medico wrote:
>> On 10/22/2015 11:29 AM, Joakim Tjernlund wrote:
>>> On Thu, 2015-10-22 at 08:54 -0700, Zac Medico wrote:
>>>> On 10/22/2015 12:05 AM, Joakim Tjernlund wrote:
>>>>> I don't use world_sets, I have in my
>>>>> profile(/my/new/root/usr/local/portage/tmv3-target-overlay):
>>>>> # > cat sets.conf
>>>>> [CUSFPv3 sets]
>>>>> class = portage.sets.files.StaticFileSet
>>>>> multiset = true
>>>>> directory = ${repository:tmv3-target-overlay}/sets/
>>>>>
>>>>> [world]
>>>>> class = portage.sets.base.DummyPackageSet
>>>>> packages = @cusfpv3 @profile @selected @system
>>>>>
>>>>> and in sets/:
>>>>> # > cat sets/cusfpv3
>>>>> net-ftp/ftp
>>>>> net-ftp/tftp-hpa
>>>>> net-ftp/vsftpd
>>>>> ....
>>>>>
>>>>> and now it hits me, this line:
>>>>> directory = ${repository:tmv3-target-overlay}/sets/
>>>>> does it always refer too ROOT=/ ?
>>>>
>>>> You need to use %(ROOT)s${repository:tmv3-target-overlay}/sets to
>>>> substitute $ROOT into the set configuration. For example, the default
>>>> set configuration located at /usr/share/portage/config/sets/portage.conf
>>>> does something similar with %(PORTAGE_CONFIGROOT)s.
>>>
>>> Nice! I am a bit puzzled over the trailing s in ..)s, is that a typo? if not
>>> what does it mean?
>>
>> The trailing s is required. It's python configparser interpolation syntax:
>>
>> https://docs.python.org/3/library/configparser.html#interpolation-of-values
>
> Looking at that URL I wonder why not use ExtendedInterpolation ?
> This would look like any other variable used in portage.
We could use it under python3, but it doesn't appear to be available for
python2.
--
Thanks,
Zac
