Re: [Netatalk-admins] Put extension mapping back in

[Frank L. <fra...@gm...>]

2012/10/15 HAT <ha...@fa...>:
> Tom Lazar <li...@to...>, 15 Oct 2012 09:52:37 +0200
>> On 14.10.2012, at 22:30, Rod Yager <ro...@ya...> wrote:
>>
>>> For what it is worth, I would suggest
>>>
>>> afp_extmap.conf
>>
>> wouldn't convention suggest that once a package has more than one configuration file, they live inside a folder of their own?
>>
>> i.e. on freebsd i would expect either
>>
>> /usr/local/etc/afp.conf
>>
>> OR
>>
>> /usr/local/etc/(afp|netatalk)/(afp.conf|extmap.conf)
>>
>> once they have their own folder, it's no longer necessary to prefix the files with afp IMHO
>
> I think we should not change a path of afp.conf any longer.

Neither I nor Tom proposed that.

> /usr/local/etc/afp.conf
> /usr/local/etc/afp_extmap.conf

Most of the times we'll see:

$configprefix/netatalk/afp.conf
$configprefix/netatalk/{extmap|afp_extmap}.conf

I'm tending towards a simple 'extmap.conf'.

> I checked the newest netatalk-doc.
> <https://github.com/Netatalk/netatalk-doc/commit/e0b586e8e8ac57ee992d97bb3b19dd3ab5f2b6f5>
>
>> extmap file = path (G)
>
> Global option!
> If it is volume option (V), it is more convenient.
> Is such change difficult?

Not really difficult, but it's not gonna happen anyway.

> I add a proposal.
> When doing "make install", "afp_extmap.conf.sample" is installed,
> not "afp_extmap.conf".
> The mapping feature is disabled by default because there is no file.
> Almost admins need do nothing because Mac OS 9 users are rare.

As you may remember, the mapping are all commented out by default, so
by default there's no mapping happening at all. Therefor this would
imo just add unneccessary complexitiy.

-f