Right now 'emerge action' and 'emerge --action' are both supported. But
as we learned with the rsync case 'emerge action' has potential
namespace conflicts with 'emerge package' I'd propose to deprecate
'emerge action' before we hit another real conflict.
(The alternative would be to deprecate
On Thursday 16 February 2006 20:31, Marius Mauch wrote:
Right now 'emerge action' and 'emerge --action' are both supported. But
as we learned with the rsync case 'emerge action' has potential
namespace conflicts with 'emerge package' I'd propose to deprecate
'emerge action' before we hit
On Thu, 16 Feb 2006 13:04:20 +
Ciaran McCreesh [EMAIL PROTECTED] wrote:
On Thu, 16 Feb 2006 12:31:25 +0100 Marius Mauch [EMAIL PROTECTED]
wrote:
| Right now 'emerge action' and 'emerge --action' are both supported.
| But as we learned with the rsync case 'emerge action' has potential
|
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
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.
