On Wed 2008-02-27 at 18:48h, Xavier Hanin wrote on ivy-user: > On Wed, Feb 27, 2008 at 6:11 PM, Niklas Matthies wrote: : > > I added a comment to the issue. Personally I haven't had the need for > > something like that in Ivy yet. It's just that I hate seeing features > > being added that let you do something (e.g. "override") to just one > > particular type of object (e.g. "revision of a transitive dependency"), > > and not for all objects where it makes sense. :) > > I usually agree, if I can envision some kind of use case for the > generalization. In this particular case I don't see what we could override > besides the revision of a transitive dependency. Do you have any idea?
How about forcing a particular configuration or branch or some extra attribute for a (set of) transitively dependent module(s)? Or overriding a (default or non-default) configuration mapping. There's probably more if I look hard enough. ;) -- Niklas Matthies
