| 1 |
iDeq ~ # /usr/bin/update-eix-remote update |
| 2 |
bash: /usr/bin/update-eix-remote: No such file or directory |
| 3 |
|
| 4 |
|
| 5 |
On 12/13/06, Alan McKinnon <alan@××××××××××××××××.za> wrote: |
| 6 |
> |
| 7 |
> On Wednesday 13 December 2006 16:32, Douglas Linford wrote: |
| 8 |
> > Good Day, |
| 9 |
> > |
| 10 |
> > I have added the eix functionallity to my system by doing the |
| 11 |
> > following: |
| 12 |
> > |
| 13 |
> > 1. iDeq ~# echo app-portage/eix >> /etc/portage/package.keywords |
| 14 |
> > 2. iDeq ~# emerge eix |
| 15 |
> > 3. iDeq ~# update-eix |
| 16 |
> > 4. iDeq ~# update-eix-remote update |
| 17 |
> > |
| 18 |
> > When I run the last command, it returns: bash: update-eix-remote: |
| 19 |
> > command not found |
| 20 |
> |
| 21 |
> Try running |
| 22 |
> |
| 23 |
> /usr/bin/update-eix-remote update |
| 24 |
> |
| 25 |
> if bash still doesn't find it, then the emerge was not successful |
| 26 |
> (unlikely) |
| 27 |
> |
| 28 |
> If bash does find the file with the full path, then you need to |
| 29 |
> run 'hash' to update bash's list of programs in the $PATH. Or just log |
| 30 |
> out and back in again |
| 31 |
> |
| 32 |
> > And when I do: slocate update-eix-remote, nothing is found. |
| 33 |
> |
| 34 |
> updatedb has not been run yet and thus does not yet know that the file |
| 35 |
> exists. Enable it in cron, or run it manually, or wait 24 hours :-) |
| 36 |
> |
| 37 |
> |
| 38 |
> alan |
| 39 |
> |
| 40 |
> -- |
| 41 |
> gentoo-user@g.o mailing list |
| 42 |
> |
| 43 |
> |
Archives