From: Gabriel C <crazy@frugalware.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [RFC] lm-sensors-3.1.0: Create /etc/sensors.d
Date: Wed, 25 Feb 2009 13:36:01 +0000 [thread overview]
Message-ID: <49A54941.3020409@frugalware.org> (raw)
In-Reply-To: <20090225084923.GA4434@ubuntu>
Jean Delvare wrote:
> Hi Andre,
>
> On Wed, 25 Feb 2009 11:20:09 +0100, Andre Prendel wrote:
>> On Wed, Feb 25, 2009 at 10:11:21AM +0100, Jean Delvare wrote:
>>> On Wed, 25 Feb 2009 09:49:23 +0100, Andre Prendel wrote:
>>>> lm-sensors-3.1.0 will introduce multiple configuration files support. The
>>>> related directory /etc/sensors.d is not created by default. Maybe we
>>>> should do that during installation, shouldn't we?
>>> I agree. While this directory isn't required, its presence will make
>>> people realize that they can put configuration files there. Want to
>>> give it a try?
>> Do you know how other packages handle such things? You are a packager
>> too, aren't you? Maybe we should leave that to the packagers?
>
> I package some projects in openSUSE but not that many, and none of them
> has an /etc/*.d directory so I can't compare. I don't see why this
> should be left to the packager. We define the default as we see fit,
> and then each packager is free to chose which file they package and
> which they don't.
>
> All I can say is that all /etc/*.d directories in openSUSE belong to at
> least one package. And sometimes the directory is empty
> (/etc/aliases.d, /etc/depmod.d). So it seems to be expected that
> packages create these directories.
>
>> Nevertheless, IMO we should provide the infrastructure (directory
>> layout) for the multiple configuration files support.
>
> Yes, I agree, let's create directory sensors.d as part of the
> installation process.
>
Maybe something like the following patch ? :
( maybe some README file in this directory won't be bad to have ? )
Index: etc/Module.mk
=================================--- etc/Module.mk (Revision 5663)
+++ etc/Module.mk (Arbeitskopie)
@@ -24,12 +24,14 @@
ETCTARGET := $(MODULE_DIR)/sensors.conf.default
ETCINSTALL := $(ETCDIR)/sensors3.conf
+ETCINSTALL_DIR_D := $(ETCDIR)/sensors.d
# No all rule
install-etc:
$(MKDIR) $(DESTDIR)$(ETCDIR)
+ $(MKDIR) $(DESTDIR)$(ETCINSTALL_DIR_D)
if [ ! -e $(DESTDIR)$(ETCINSTALL) ] ; then \
$(INSTALL) -m 644 $(ETCTARGET) $(DESTDIR)$(ETCINSTALL); \
fi
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2009-02-25 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 8:49 [lm-sensors] [RFC] lm-sensors-3.1.0: Create /etc/sensors.d during Andre Prendel
2009-02-25 9:11 ` [lm-sensors] [RFC] lm-sensors-3.1.0: Create /etc/sensors.d Jean Delvare
2009-02-25 10:20 ` Andre Prendel
2009-02-25 12:14 ` Jean Delvare
2009-02-25 13:36 ` Gabriel C [this message]
2009-02-26 9:45 ` Jean Delvare
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49A54941.3020409@frugalware.org \
--to=crazy@frugalware.org \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.