On Wed, 10 Sep 2008 01:43:45 +0100 Steve Long <[EMAIL PROTECTED]> wrote:
> Marius Mauch wrote: > > > Second for the suggestions on how to handle the transition: > > - treating 'world' and '@world' differently is a no go from my POV. > > One of the main reasons to implement them as sets was to remove > > special case code in emerge, so I'm quite opposed to adding new > > special cases instead. And I'm quite sure that such a separation > > would cause confusion, and some isues regarding (end-user) > > documentation. > > We're talking about one special case in the command-line processing, > to support the existing usage that all our users are used to. It adds > practically nothing in execution time, simply expanding to @system > @world, and means that users who don't want to know about sets, or > are not thinking in set terms at the time of using emerge, will get > the result they expect. It also means we'd indefinitely have to carry another special case around for legacy reasons (removing it later would be even more painful than doing the switch now). You know, those are the things we want to get rid off, as they really make our life harder in the long run. YOu may consider it trivial in this cse, but these things always look trivial when you're adding them, and you curse about them when you have to modify the code later on. Maybe the best solution is to drop the non-prefixed versions of 'world' and 'system' completely .... Marius
