Commit 5380720f authored by Richard Hughes's avatar Richard Hughes

Move the udev rules to thier own directory

parent db414832
## Process this file with automake to produce Makefile.in
SUBDIRS = devkit-power-gobject src doc tools policy po
SUBDIRS = devkit-power-gobject src doc tools policy po rules
# Creating ChangeLog from git log (taken from cairo/Makefile.am):
ChangeLog: $(srcdir)/ChangeLog
......
......@@ -189,6 +189,7 @@ doc/version.xml
doc/man/Makefile
doc/dbus/Makefile
policy/Makefile
rules/Makefile
devkit-power-gobject/Makefile
devkit-power-gobject/dkp-version.h
po/Makefile.in
......
## Process this file with automake to produce Makefile.in
udevrulesdir = $(slashlibdir)/udev/rules.d
udevrules_DATA = \
95-devkit-power-battery-recall-dell.rules \
95-devkit-power-battery-recall-fujitsu.rules \
95-devkit-power-battery-recall-gateway.rules \
95-devkit-power-battery-recall-ibm.rules \
95-devkit-power-battery-recall-lenovo.rules \
95-devkit-power-battery-recall-toshiba.rules \
95-devkit-power-wup.rules \
95-devkit-power-hid.rules \
95-devkit-power-csr.rules
EXTRA_DIST = \
$(udevrules_DATA)
clean-local :
rm -f *~
......@@ -109,18 +109,6 @@ dbusconf_DATA = $(dbusconf_in_files:.conf.in=.conf)
$(dbusconf_DATA): $(dbusconf_in_files) Makefile
cp $< $@
udevrulesdir = $(slashlibdir)/udev/rules.d
udevrules_DATA = \
95-devkit-power-battery-recall-dell.rules \
95-devkit-power-battery-recall-fujitsu.rules \
95-devkit-power-battery-recall-gateway.rules \
95-devkit-power-battery-recall-ibm.rules \
95-devkit-power-battery-recall-lenovo.rules \
95-devkit-power-battery-recall-toshiba.rules \
95-devkit-power-wup.rules \
95-devkit-power-hid.rules \
95-devkit-power-csr.rules
install-data-hook:
if test -w $(DESTDIR)$(prefix)/; then \
mkdir -p $(DESTDIR)$(localstatedir)/lib/DeviceKit-power; \
......@@ -134,7 +122,6 @@ EXTRA_DIST = \
org.freedesktop.DeviceKit.Power.QoS.xml \
org.freedesktop.DeviceKit.Power.Wakeups.xml \
dkp-marshal.list \
$(udevrules_DATA) \
$(service_in_files) \
$(dbusconf_in_files)
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment