public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/4] packaging: allow globs in CONFFILES
Date: Fri, 19 Dec 2014 07:42:24 +0100	[thread overview]
Message-ID: <5493C8D0.1040907@topic.nl> (raw)
In-Reply-To: <084ad3c5c70057e5f8f06bf85b4543a590a17a54.1418969925.git.Qi.Chen@windriver.com>

On 12/19/2014 07:21 AM, Chen Qi wrote:
 > ...
> As almost all files under /etc are basically configuration files, we
> provide a default value for CONFFILES.
>
>      CONNFFILES = "${sysconfdir}"

This is going to hurt a lot of recipes. Please do not set this.

The default has always been that CONFFILES is empty. I see no reason 
whatsoever to suddenly change this.

> In this way, we don't need to modify every recipe to set the CONFFILES
> variable. Of course, setting CONFFILES in recipes take precedence over
> the CONFFILES. For example, if the recipe author decides that package A
> should only treat files under ${sysconfdir}/default/ as config files,
> he/she can write like this.
>
>      CONFFILES_A = "${sysconfdir}/default"
>
> The above situation should not be common. As according to FHS, the /etc
> directory is a place for all system related configuration files.

FHS may have written that somewhere, but if you just take a quick look at what 
is in /etc/, you'll find that actual configuration files are quite rare, but 
there are tons of scripts and distro related files there. Whether or not a 
file there is supposed to be edited by the end-user is something of a distro 
decision.

Also, "configuration file" does not necessarily mean that the USER is in 
control. A configuration file may also simply distinguish machine capabilities 
or software features.

We'll end up having to patch hundreds of recipes with a CONFFILES="" or 
similar line.


Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax:  (+31) (0) 499 33 69 70
E-mail: mike.looijmans@topic.nl
Website: www.topic.nl

Please consider the environment before printing this e-mail

Topic zoekt gedreven (embedded) software specialisten!
http://topic.nl/vacatures/topic-zoekt-software-engineers/



  reply	other threads:[~2014-12-19  6:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-19  6:21 [PATCH V2 0/4] Change the way of CONFFILES handling Chen Qi
2014-12-19  6:21 ` [PATCH 1/4] packaging: allow globs in CONFFILES Chen Qi
2014-12-19  6:42   ` Mike Looijmans [this message]
2014-12-23  1:56     ` ChenQi
2014-12-23  6:25       ` Anders Darander
2014-12-23  8:44         ` ChenQi
2014-12-19  6:21 ` [PATCH 2/4] package_manager.py: user 'purge' instead of 'remove' in case of deb Chen Qi
2014-12-19  6:21 ` [PATCH 3/4] update-rc.d: use '-f' option in updatercd_postrm Chen Qi
2014-12-19  6:21 ` [PATCH 4/4] useradd.bbclass: avoid do_rootfs error for debian package backend Chen Qi

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=5493C8D0.1040907@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox