Hello all!
I am a Gentoo n00b. I have question about what the 'expected
behaviour' is/should be when removing packages under Gentoo package
management. So I read this document:
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?style=printablefull=1#book_part2
And it says, to remove
On Mon, 4 May 2009 10:45:00 +0100, Matt Causey wrote:
Sooo, my question. What is the expected behaviour here? Are the
ebuilds intended to maintain knowledge of the files they put on a
system, so they can remove the binaries when --unmerge'd? Are kernel
modules handled differently because
Neil Bothwick schrieb:
On Mon, 4 May 2009 10:45:00 +0100, Matt Causey wrote:
Sooo, my question. What is the expected behaviour here? Are the
ebuilds intended to maintain knowledge of the files they put on a
system, so they can remove the binaries when --unmerge'd? Are kernel
modules
On Monday 04 May 2009 11:45:00 Matt Causey wrote:
Hello all!
I am a Gentoo n00b. I have question about what the 'expected
behaviour' is/should be when removing packages under Gentoo package
management. So I read this document:
Out of tree kernel modules are a maintenance pain in the ass, and cause
severely non-obvious problems like this. Every time you upgrade your kernel,
you must rebuild the out-of-tree modules, and you do that by re-running
emerge madwifi-ng. This builds a new modules that matches the currently
On Monday 04 May 2009 14:11:02 Matt Causey wrote:
Out of tree kernel modules are a maintenance pain in the ass, and cause
severely non-obvious problems like this. Every time you upgrade your
kernel, you must rebuild the out-of-tree modules, and you do that by
re-running emerge madwifi-ng.
On Mon, 4 May 2009 13:11:02 +0100
Matt Causey matt.cau...@gmail.com wrote:
--snip--
Along the same lines, how does the ebuild know what to remove on
--unmerge? For example I'm wandering around and looking at ebuilds:
prometheus ethtool # pwd
/usr/portage/sys-apps/ethtool
prometheus
7 matches
Mail list logo
