Summary: | new ebuild: x86info 1.11 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Arun Thomas (RETIRED) <sindian> |
Component: | New packages | Assignee: | Martin Schlemmer (RETIRED) <azarah> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | robbat2, sindian |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.codemonkey.org.uk/x86info/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
the actual ebuild
modules.d file Updated ebuild tarball(obsoletes others) |
Description
Arun Thomas (RETIRED)
2003-01-31 21:08:13 UTC
Created attachment 7795 [details]
the actual ebuild
This is the ebuild.
Created attachment 7796 [details]
modules.d file
This is the modules.d file.
By the way, I ran lintool on the ebuild, and it reported no errors. Again, I'd be more than happy to fix problems. Thanks again, Arun Also, there are no sandbox violations as far as I can tell. I didn't notice this pending item when I wrote up a new ebuild for x86info myself now. I've taken some of the items from here and merged them into my ebuild now. File listing: ChangeLog x86info-1.11.ebuild files/digest-x86info-1.11 files/x86info-modules.conf-rc My modules.d/x86info includes the content of Arun's, but also adds two more lines to allow for better automatic probing of modules as needed. As regarding the device nodes: There are 3 methods scattered in the portage tree for this. app-misc/toshiba-utils makes the devices notes when you call the config function. media-video/dxr2-driver makes the devices during the install stage net-wireless/bluez-utils and net-dialup/ppp make them during the postinstall stage. I think creating them automatically during the postinstall stage is the best way, and it also seems to be most common, so i've followed it. I don't think the config one is good, since it requires more input from the user that is just brainless. If you would prefer one of the other methods however, leave a note here and I'll do it up quickly. my ebuild also includes the same warning that Arun had. Arun's ebuild didn't use the CFLAGS setting in building the binaries, and mine does. Arun's ebuild didn't include the results/ documentation directory tree, which I have included (compressed with a call to prepalldocs). This ebuild passes lintool, and I've tested it on the following (all on gentoo 1.4 with ARCH="~x86"): VIA C3 Samuel 600mhz AMD Athlon(tm) XP 1800+ Pentium III (Katmai) 500mhz [overclocked to 515mhz] Tarball attached. Created attachment 10001 [details]
Updated ebuild tarball(obsoletes others)
This obsoletes both other attachments.
ok, this is in unstable under sys-apps/x86info Closing bug properly. |