[ baselayout-1.11.14 -> udev ] [ solved ]

[FLYLM]

Hi,

I use kernel 2.4.x and since this morning, the update of "sys-apps/baselayout-1.11.14" needs "udev".
I don't want to use "udev". Is existing a way to update "baselayout" without "udev" ? Or should i stay with "baselayout-1.11.13-r1" ?

Thanks.

(sorry for my poor english)

[ecatmur]

Unstable unmask sys-fs/devfsd-1.3.25-r9.
_________________
No more cruft
dep: Revdeps that work
Using command-line ACCEPT_KEYWORDS?

[FLYLM]

Thanks for your help !

Now, emerge of baselayout don't need "udev".

[laoshi]

have same problem ... what do u mean with unstable unmask?
portage tells me that devfs version seems not to be masked.

[ecatmur]

Use /etc/portage/package.keywords. If you're already running unstable you don't need to.
_________________
No more cruft
dep: Revdeps that work
Using command-line ACCEPT_KEYWORDS?

[FLYLM]

I'm wondering why when an update of "devfsd" is available (devfsd-1.3.25-r9) but not installed, emerge -pDu world continue to want to install "udev" ?
I know that "devfsd" is not in the list of world's packages, but i find that the behavior of emerge is not good ? What do u think about that ?

[ecatmur]

Difficult to say; it does seem odd behaviour. It could simply be because udev is preferred over devfs.
_________________
No more cruft
dep: Revdeps that work
Using command-line ACCEPT_KEYWORDS?

[FLYLM]

[ecatmur]

Well, no; switching to an alternative dependency resolution does make sense in most cases; for example, on ppc packages that need Java 1.4 should bring in ibm-jdk-1.4 even if blackdown 1.3 is installed.

If you strongly prefer devfsd to udev you could mask udev, I guess.
_________________
No more cruft
dep: Revdeps that work
Using command-line ACCEPT_KEYWORDS?

[FLYLM]

Ok, thanks for your explanation.