On Friday 17 February 2006 05:30, solar wrote:
> On Thu, 2006-02-16 at 19:04 +0100, Marius Mauch wrote:
>
> [snip]
>
> > > If by "deprecate" you mean to detect when '--' hasn't been prepended
> > > and either go ahead with the action or notify that the package
> > > doesn't exist then I have no objections. Might be better to go with
> > > the latter so that users adjust quickly.
> >
> > You saw the attached one-line patch?
Heh. Actually I completely missed it.
> > Atm it just throws a warning when an action without -- is used.
> > I'm divided on ignoring the action then, on one hand it would be nice to
> > get rid of this, OTOH it would be kinda rude to not have a transition
> > period for people. Anyone else having an opinion on this?
>
> I agree it would be kinda rude to just deprecate a behavior and
> introduce another all in one shot. I'd give it a few releases till
> people retrain themselves.
> Maybe when emerge --world/--system/--action has worked it's way into
> at least 2 stable releases before deprecating 'action'
This brings up an interesting point. "emerge --world" really should fail as
not being valid as it is not an action but a target. With the goal of having
targets user configurable, treating them as options really doesn't work.
So, I'm also moving toward just printing warnings for the time being.
However, we should probably figure out exactly how it should work and then
print warnings whenever any deprecated syntax is used. Not so much for users
and scripts, of which I can't see there being much of a problem, but so that
we can redo that whole bunch of code without having to do:
if incorrect_syntax:
print warning
make correct syntax
--
Jason Stubbs
--
[email protected] mailing list
