| 1 |
On 30/05/2003 at 02:03:52(-0500), Matthew Kennedy used 2.2Kbytes just to say: |
| 2 |
> 2. what to do when the user does try to emerge an ambiguously named |
| 3 |
> short-form package name. |
| 4 |
> |
| 5 |
> In the second case you could have: |
| 6 |
> |
| 7 |
> 1. emerge the first foo portage finds (undesirable, but what happens |
| 8 |
> currently) |
| 9 |
> |
| 10 |
> 2. prompt interactively (this would be the first time portage |
| 11 |
> prompts for user interaction afaik) |
| 12 |
> |
| 13 |
> 3. fail with an error message indication a long-form etc. must be |
| 14 |
> given to resolve one or more packages. |
| 15 |
> |
| 16 |
> I don't really care either way between 2 and 3. |
| 17 |
|
| 18 |
Shouldn't we define what "ambiguous" is? After all let's not forget that the |
| 19 |
worst case is: |
| 20 |
|
| 21 |
emerge rsync vs. emerge net-misc/rsync |
| 22 |
|
| 23 |
Currently, only option 1 works with "emerge rsync". Maybe a warning should be |
| 24 |
given every time a user tries to "emerge rsync" so that they get used to the |
| 25 |
alias sync. |
| 26 |
|
| 27 |
-- |
| 28 |
/^^^^^^^^^^^^^^^^^^^^^^^^^^^\/^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\ |
| 29 |
/ Georgi Georgiev (-< / Chance is perhaps the work of \ |
| 30 |
\ chutz@×××××××.net /\ .o)\ God when He did not want to / |
| 31 |
/ +81(90)6266-1163 V_/_ |(/)/ sign. -- Anatole France \ |
| 32 |
\___________________________/\__________________________________/ |
| 33 |
|
| 34 |
-- |
| 35 |
gentoo-dev@g.o mailing list |
Archives