| 1 |
On Wed, 16 Apr 2003, Peter Ruskin wrote: |
| 2 |
|
| 3 |
> On Wednesday 16 Apr 2003 01:58, Dave Nellans wrote: |
| 4 |
> > The question then remains is how to determine which package is the |
| 5 |
> > "default" to be installed if you use only the ebuild name. I haven't |
| 6 |
> > poked in the code to see how portage is doing it now, but can see three |
| 7 |
> > possible options. One being alphabetical by category, two being first |
| 8 |
> > come first serve, or three allowing the "most commonly installed" of |
| 9 |
> > the options defined by whomever is maintaining the package(s). The |
| 10 |
> > only downside is that portage/ebuilds will need yet another thing added |
| 11 |
> > to it similar to SLOTS to help support this =/ |
| 12 |
> |
| 13 |
> Or perhaps better, emerge should fail and print a message like: |
| 14 |
> "There is more than one package with that name. Please use |
| 15 |
> 'emerge <category>/<package>.ebuild' for the required package.'" |
| 16 |
> |
| 17 |
> Peter |
| 18 |
|
| 19 |
This defenitely makes the most sense. The user will know which app they |
| 20 |
want to emerge so portage should ask them rather than just installing some |
| 21 |
default app that they really don't want on their machine. Problem |
| 22 |
solved... |
| 23 |
|
| 24 |
-Jeff |
| 25 |
|
| 26 |
|
| 27 |
|
| 28 |
-- |
| 29 |
gentoo-dev@g.o mailing list |
Archives