This is indeed what I was trying to describe, thanks Jeff. The only
issue I can think of is how to report how far back up the rabbit hole
you have to go to find the origination point for a particular value.
Maybe somthing along the lines of
<<parent_profile::value>>
Or
<<::value>>
The second one having a ":" for every level of indirection. Although
more compact, it doesn't give much info, so I prefer the first option
above.
Regards,
Corey
On Feb 2, 2009, at 4:46, Jeff Schroeder <jeffschroed(a)gmail.com> wrote:
On Sun, Feb 1, 2009 at 7:59 PM, Michael DeHaan
<mdehaan(a)redhat.com>
wrote:
> Corey Kovacs wrote:
>> Got it, thanks. Seems like it would be helpful to see the parent
>> options, perhaps displayed in a similar way <<inherit>> is now but
>> list the value instead as in <<2048>> for your ram example. Keep the
>> double arrows to mean 'value is inherited'. Just a thought.
>>
>> Regards,
>>
>> Corey
>>
>
> Something like this could be doable, though we might want to make
> it a
> bit nicer. "<<inherit>>" as a value
> actually means something to cobbler.
>
> Also, hash and array variables are extended, not just overridden.
>
> I'm thinking more like a "cobbler system report --actual" to show all
> the values that are filled in, maybe, which would
> be pretty easy to do.
I think he was trying to say that should be the default. On that one,
I tend to agree. Why not have the value in the system entry be inherit
and the have "cobbler system report" grab it from the profile it is
inherited from? Putting << >> around the inherited entry is also a
good idea as it gives you an idea where the value is coming from.
--
Jeff Schroeder
Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler