On 08/18/2009 04:51 PM, Klaus Kaempf wrote:
> * Josef Reidinger <[email protected]> [Aug 18. 2009 15:53]:
>> On 08/18/2009 10:37 AM, Klaus Kaempf wrote:
>>> Hi,
>>>
>>> the requirements for WebYaST contain a couple of vendor-configurable
>>> parts. Some are on the frontend (branding), some on the backend (setup
>>> workflow, services, ...).
>>>
>>> The current approach is to implement vendor configurations spread
>>> among many backend modules.
>>>
>>> I wonder if this is the right approach and if it wouldn't be better to
>>> have a single, shared implementation (class ? service ?) to cover this
>>> all.
>>>
>>> A single implementation would ensure consistency in file formats and
>>> locations as well as a single documentation.
>>>
>>> This is mostly for Josef and Jiri to agree upon ;-)
>>>
>>> Klaus
>>
>> Yes, I agree.
>> We should have allocated place (like somewhere in /etc/YaST2) I only
>> need read permissions to this file.
>
> Actually, I would suggest to use /etc/webyast as to not confuse it with
> other YaST2 settings.
>
Yes, and I think that this path should be enclosed in that abstract
class for loading configuration, so you use just
conf = ConfLoader.load("basesystem.conf")
and doesn't care where is real destination (and we can easy change it in
future if we agree on better location).
--
Josef Reidinger
YaST team
maintainer of perl-Bootloader, YaST2-Repair, webyast modules language
and time
--
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
