I'm puzzled trying to use `emerge clean'.
From its man page (in part):
clean (-c)
Cleans the system by removing packages that will not effect the
functionality of the system. The arguments can be ebuilds,
classes, or dependencies. For example, emerge clean binutils
cleans out old versions of binutils; emerge clean
net-www/mozilla-0.9.9-r2 cleans out that specific version of
Mozilla. This is generally safe to use. Note that clean does
not remove unslotted packages.
This seems to indicate I could get rid of metalog like this:
But instead it gives me:
# emerge clean app-admin/metalog
>>> clean: No packages selected for removal.
Or:
Now to find the exact version of metalog, one would expect qpkg to
return the name and version:
# qpkg -f /usr/sbin/metalog
app-admin/metalog *
But instead it leaves you wondering what version.
But still maybe this can work with `emerge clean'
Err no ooops:
# emerge clean app-admin/metalog *
--- Couldn't find installed to clean.
--- Couldn't find nbk to clean.
--- Couldn't find uninstalled to clean.
--- Couldn't find uninstalled~ to clean.
>>> clean: No packages selected for removal.
OK so how does one satisfy `emerge clean' syntax?
# ls /usr/portage/app-admin/metalog
ChangeLog Manifest files metalog-0.7-r1.ebuild
metalog-0.8_pre20031130.ebuild
Ahh here we go.
# emerge clean metalog-0.7-r1
--- Couldn't find metalog-0.7-r1 to clean.
>>> clean: No packages selected for removal.
# emerge clean metalog-0.8_pre20031130
>>> clean: No packages selected for removal.
OK so we can't learn the exact version from qpkg nor can we `clean'
without that version.
Maybe we can get the version from metalog itself...
metalog --help
metalog version 0.7
[...]
Ahh there it is...
# emerge clean metalog-0.7
--- Couldn't find metalog-0.7 to clean.
>>> clean: No packages selected for removal.
What is the answer to this quandry?
--
gentoo-user@gentoo.org mailing list
From its man page (in part):
clean (-c)
Cleans the system by removing packages that will not effect the
functionality of the system. The arguments can be ebuilds,
classes, or dependencies. For example, emerge clean binutils
cleans out old versions of binutils; emerge clean
net-www/mozilla-0.9.9-r2 cleans out that specific version of
Mozilla. This is generally safe to use. Note that clean does
not remove unslotted packages.
This seems to indicate I could get rid of metalog like this:
But instead it gives me:
# emerge clean app-admin/metalog
>>> clean: No packages selected for removal.
Or:
Now to find the exact version of metalog, one would expect qpkg to
return the name and version:
# qpkg -f /usr/sbin/metalog
app-admin/metalog *
But instead it leaves you wondering what version.
But still maybe this can work with `emerge clean'
Err no ooops:
# emerge clean app-admin/metalog *
--- Couldn't find installed to clean.
--- Couldn't find nbk to clean.
--- Couldn't find uninstalled to clean.
--- Couldn't find uninstalled~ to clean.
>>> clean: No packages selected for removal.
OK so how does one satisfy `emerge clean' syntax?
# ls /usr/portage/app-admin/metalog
ChangeLog Manifest files metalog-0.7-r1.ebuild
metalog-0.8_pre20031130.ebuild
Ahh here we go.
# emerge clean metalog-0.7-r1
--- Couldn't find metalog-0.7-r1 to clean.
>>> clean: No packages selected for removal.
# emerge clean metalog-0.8_pre20031130
>>> clean: No packages selected for removal.
OK so we can't learn the exact version from qpkg nor can we `clean'
without that version.
Maybe we can get the version from metalog itself...
metalog --help
metalog version 0.7
[...]
Ahh there it is...
# emerge clean metalog-0.7
--- Couldn't find metalog-0.7 to clean.
>>> clean: No packages selected for removal.
What is the answer to this quandry?
--
gentoo-user@gentoo.org mailing list