1 |
>>>>> On Thu, 5 Nov 2015, David Leverton wrote: |
2 |
|
3 |
> Ulrich Müller wrote: |
4 |
>> +\featurelabel{profile-file-dirs} For EAPIs listed as supported in table~\ref{tab:profile-file-dirs}, |
5 |
>> +simple line-based files described in the following sections may optionally be directories containing |
6 |
>> +files of the named type. |
7 |
|
8 |
> 1) Can those directories themselves contain subdirectories (and |
9 |
> sub-subdirectories, ...), or is it just one level deep? |
10 |
|
11 |
> 2) Is there any restriction on the names of the files (e.g. ignoring |
12 |
> hidden files, editor backups, etc), or can they be anything? |
13 |
|
14 |
> If I'm reading the current Portage implementation correctly, the |
15 |
> answers there (without making any claims about what the spec should |
16 |
> or shouldn't adopt) are: |
17 |
|
18 |
> 1) Yes, there can be multiple levels of subdirectories. |
19 |
|
20 |
> 2) Yes, files and subdirectories beginning with a . or ending with a |
21 |
> ~ are excluded, as are subdirectories named CVS, RCS or SCCS. |
22 |
|
23 |
From the wording that we have it seems that the answer to both |
24 |
questions should be No. |
25 |
|
26 |
I'll try to have this clarified before the council meeting. If that |
27 |
should fail, I suggest to drop the feature from EAPI 6; it can be |
28 |
reconsidered for EAPI 7 then. |
29 |
|
30 |
Ulrich |