>>> Source unpacked in /usr/i586-geode-linux-gnu/tmp/portage/sys-fs/static-dev-0.1/work >>> Compiling source in /usr/i586-geode-linux-gnu/tmp/portage/sys-fs/static-dev-0.1/work ... >>> Source compiled. >>> Test phase [not enabled]: sys-fs/static-dev-0.1 >>> Install static-dev-0.1 into /usr/i586-geode-linux-gnu/tmp/portage/sys-fs/static-dev-0.1/image/ category sys-fs * Using generic-i386 to make x86 device nodes... don't know how to make device "generic-i386" >>> Completed installing static-dev-0.1 into /usr/i586-geode-linux-gnu/tmp/portage/sys-fs/static-dev-0.1/image/ It seems that using sys-apps/makedev it doesn't recognize anymore generic-XXX. But "profiles" in /etc/makedev.d don't work for all : # MAKEDEV -D/tmp/de generic # MAKEDEV -D/tmp/de linux-2.6.x don't know how to make device "linux-2.6.x" Reproducible: Always Steps to Reproduce: 1. i586-geode-linux-gnu-emerge -at static-dev 2. 3.
Created attachment 280455 [details, diff] static-dev-0.1.ebuild-BJA-classes.diff I get a responce from Nalin Dahyabhai, the MAKEDEV maintainer : > Because the tool will take any value passed on the command line as a > possible initial portion of a device node to make, you can likely get > what you're after by running it with "" as a parameter. > > There's some information duplicated between the various linux-* > configuration files, and some of it (ia64, s390) is > architecture-specific, so you'll want to prune out the stuff you don't > need, first. So here is a patch to ebuild to build "generic sda sdb sdc ptmx ram rtc" only by default and let user define EXTRA_CLASSES to build more static dev classes as defined in makedev.d/*
if people want extra nodes they can make it themselves http://sources.gentoo.org/sys-fs/static-dev/static-dev-0.1.ebuild?r1=1.13&r2=1.14
Using a env variable to set extra nodes have the advantage to create proper packages. I was also thinking to redefine generic-XXX as they were in old MAKEDEV shell script. What do you think about it ?
users can just as easily run `MAKEDEV` as set an env var. the device nodes dont "belong" to any package, so they wont be unmerged.
(In reply to comment #4) > users can just as easily run `MAKEDEV` as set an env var. the device nodes > dont "belong" to any package, so they wont be unmerged. I mean when you use buildpkg FEATURES
