Summary: | net-wireless/urfkill (new package) - Handler for rfkill events in userspace | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marco Paolone <marcopaolone> |
Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
Status: | UNCONFIRMED --- | ||
Severity: | enhancement | CC: | leho |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.freedesktop.org/wiki/Software/urfkill | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
urfkill ebuild
init.d urfkill script xdg autostart file startup script for X session urfkill ebuild fixed new fix for urfkill ebuild init.d urfkilld script fixed |
Description
Marco Paolone
2011-05-12 16:33:10 UTC
Created attachment 272951 [details]
urfkill ebuild
Created attachment 272953 [details]
init.d urfkill script
Created attachment 272955 [details]
xdg autostart file
Created attachment 272957 [details]
startup script for X session
i'm pretty sure samuli said in another bug (i think pambase, consolekit and CONFIG_AUDITSYSCALL related) that current policy is not to die on missing kernel configuration options. looks like we're dying here with missing CONFIG_RFKILL. econf will also die because of the commented line: config.status: executing po/stamp-it commands /var/tmp/portage/net-wireless/urfkill-0.1.1/temp/environment: line 3010: --disable-dependency-tracking: command not found * ERROR: net-wireless/urfkill-0.1.1 failed (configure phase): * econf failed Created attachment 273477 [details]
urfkill ebuild fixed
Fixed. Thanks :) ebuild isn't creating /etc/init.d/urfkilld for me, isn't that what newinitd is supposed to do? Created attachment 273491 [details]
new fix for urfkill ebuild
Created attachment 273493 [details]
init.d urfkilld script fixed
Forgot a parameter for newinitd in ebuild, and fixed init script too. I see that it's marked only for ~x86; Could be emerging on amd64 problematic? (In reply to comment #13) > I see that it's marked only for ~x86; Could be emerging on amd64 problematic? No, it shouldn't be problematic. If it works for you I'll add ~amd64 in a later revision of ebuild. |