On Thu, Dec 10, 2009 at 12:27, Felix Meschberger <fmesc...@gmail.com> wrote:
> Alexander Klimetschek schrieb:
>> I also think that the merging for my proposed case isn't that
>> difficult: you just walk the tree below /etc/map as it is done now and
>> apply things for the runmode they are in (defined by the ancestor).
>> First come, first served for duplicate mappings. That is the same as
>> for implementing O2. The only difference are those "empty" folders
>> that don't add to the mapping config, but just specify the runmode(s).
>
> It is more involved...

AFAICS the /etc/map tree is traversed from top to bottom while the
config is built up, so on each step, before the traversal goes deeper
and/or creates a final map entry config, it could simply check for the
runmodes property and/or if this is an "empty" folder (this could eg.
be marked by the property being present or by a mixin). If the
runmode(s) don't match, it won't traverse deeper.

What am I missing?

Regards,
Alex

-- 
Alexander Klimetschek
alexander.klimetsc...@day.com

Reply via email to