| 1 |
On Thu, 01 Sep 2011 16:16:05 +0200 |
| 2 |
Florian Philipp <lists@×××××××××××.net> wrote: |
| 3 |
|
| 4 |
> Am 01.09.2011 15:47, schrieb Doug Hunley: |
| 5 |
> > On Wed, Aug 31, 2011 at 22:32, Pandu Poluan <pandu@××××××.info> |
| 6 |
> > wrote: |
| 7 |
> >> Why do you want to unmerge net-tools, anyway? |
| 8 |
> > |
| 9 |
> > 'equery depends' shows that nothing needs it, and why keep an entire |
| 10 |
> > package around when I have another package installed that does what |
| 11 |
> > the first package is supposed to do? ;) |
| 12 |
> > |
| 13 |
> |
| 14 |
> |
| 15 |
> `emerge -pv --depclean sys-apps/net-tools` is more reliable than |
| 16 |
> equery for finding dependencies. It will tell you that net-tools is |
| 17 |
> part of @system. It is generally discouraged for ebuild-developers to |
| 18 |
> add dependencies to stuff that belongs to @system. Therefore equery |
| 19 |
> does not help you find all dependencies. |
| 20 |
> |
| 21 |
> If you are so eager to remove net-tools, you can try to replace all |
| 22 |
> binaries with symlinks to /bin/busybox. It should contain minimal |
| 23 |
> implementations for most binaries like hostname. Note that this can |
| 24 |
> seriously break your system if the busybox implementation is |
| 25 |
> insufficient. |
| 26 |
|
| 27 |
*Especially* don't use BusyBox tar. |
| 28 |
|
| 29 |
Been there, done that. |
| 30 |
|
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
Alan McKinnnon |
| 35 |
Systems Engineer^W Technician |
| 36 |
Internet Solutions |
| 37 |
|
| 38 |
011 575 7585 |
| 39 |
alan.mckinnon@×××××.za |
Archives