From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 3/3] base-files-3.0.14 configuration files
Date: Thu, 17 Mar 2011 11:10:58 +0000 [thread overview]
Message-ID: <1300360258.2132.14668.camel@phil-desktop> (raw)
In-Reply-To: <201103171154.23397.pgsellmann@portner-elektronik.at>
On Thu, 2011-03-17 at 11:54 +0100, Peter Gsellmann wrote:
> Mark some files in ${sysconfdir} as configuration files so they are not blindly overwritten when upgrading
I wonder if it would make sense to mark everything in ${sysconfdir} and
${sysconfdir}/default (but probably not other subdirs) as a conffile
automatically. I don't think there are many/any files in there that
wouldn't want conffile treatment.
> -CONFFILES_${PN} = "${sysconfdir}/fstab ${sysconfdir}/hostname"
> +CONFFILES_${PN} = "${sysconfdir}/fstab ${sysconfdir}/hostname ${sysconfdir}/motd \
> + ${sysconfdir}/profile ${sysconfdir}/nsswitch.conf ${sysconfdir}/host.conf"
> CONFFILES_${PN}_micro = ""
> CONFFILES_${PN}_nylon = "${sysconfdir}/resolv.conf ${sysconfdir}/fstab ${sysconfdir}/hostname"
> CONFFILES_${PN}_slugos = "${sysconfdir}/resolv.conf ${sysconfdir}/fstab ${sysconfdir}/hostname"
Those DISTRO overrides look a bit weird too. I wonder if the slugos and
nylon ones ought really to be "CONFFILES_${PN}_prepend_DISTRO" or
something. The intent of the micro one is fairly clear although I can't
immediately think why this would be useful given that micro doesn't use
O_P_M.
p.
next prev parent reply other threads:[~2011-03-17 11:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 10:54 [PATCH 3/3] base-files-3.0.14 configuration files Peter Gsellmann
2011-03-17 11:10 ` Phil Blundell [this message]
2011-03-17 12:53 ` Hauser, Wolfgang (external)
2011-03-17 15:54 ` Peter Gsellmann
2011-03-18 8:59 ` Hauser, Wolfgang (external)
2011-03-18 10:56 ` Phil Blundell
2011-03-21 9:11 ` Hauser, Wolfgang (external)
2011-03-18 13:08 ` Peter Gsellmann
2011-03-18 15:30 ` Martin Jansa
2011-03-18 17:37 ` Peter Gsellmann
2011-03-21 9:30 ` Martin Jansa
2011-03-21 11:36 ` Peter Gsellmann
2011-03-21 11:54 ` Phil Blundell
2011-03-21 12:33 ` Peter Gsellmann
2011-03-21 13:58 ` Phil Blundell
2011-03-21 14:18 ` Peter Gsellmann
2011-03-21 12:53 ` [PATCH v2] " Peter Gsellmann
2011-03-21 16:39 ` Phil Blundell
2011-03-21 18:19 ` Peter Gsellmann
2011-03-22 11:17 ` [PATCH v3] " Peter Gsellmann
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=1300360258.2132.14668.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-devel@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 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.