From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: David Vincent <freesilicon@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] openssl: Fix symlink creation
Date: Thu, 20 Apr 2017 15:37:24 +0300 [thread overview]
Message-ID: <d67f6cb5-482e-9e3f-bde5-4284e8eeb31b@linux.intel.com> (raw)
In-Reply-To: <5023360.N8L8OyXh3V@crde-port-20.cahors.local>
On 04/19/2017 04:03 PM, David Vincent wrote:
> The problem is that I must be able to manage the configuration of a machine
> without physical intervention and only via package upgrades. A new
> configuration can be applied simply by incrementing the PR of a configuration
> package.
>
> But maybe this is a use case only needed by me and I should manage it in my
> own specific layer ?
>
> Now that I think of it, I have the same kind of problem for all machine
> specific configurations. For now, I just replace the PACKAGE_ARCH in my BSP
> layer with a machine specific one to indicate that a package contains a
> configuration valid only for a specific machine. Maybe, in a future release, it
> should be desirable to create -conf packages based on the CONFFILES variable ?
> I don't know if it's a good idea, but maybe I could bring that up on the
> architecture mailing list ?
By all means please do so. Yocto lacks a solution for configuration
management, and this was discussed some time ago, although I cannot
anymore find where it happened. Mark, do you remember?
Alex
next prev parent reply other threads:[~2017-04-20 12:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 13:59 [PATCH] openssl: Fix symlink creation David Vincent
2017-04-05 7:30 ` Jussi Kukkonen
2017-04-06 9:23 ` David Vincent
2017-04-06 10:55 ` Jussi Kukkonen
2017-04-06 13:03 ` Martin Jansa
2017-04-07 12:27 ` David Vincent
2017-04-07 12:52 ` Jussi Kukkonen
2017-04-07 13:09 ` Martin Jansa
[not found] ` <CAHiDW_EQL63FQt7t8fETRZkx0sVjNs-as5Y+qexN48CtCUS5MQ@mail.gmail.com>
2017-04-19 8:27 ` David Vincent
2017-04-19 10:21 ` Alexander Kanavin
2017-04-19 11:53 ` David Vincent
2017-04-19 11:57 ` Alexander Kanavin
2017-04-19 12:56 ` Alexander Kanavin
2017-04-19 13:03 ` David Vincent
2017-04-20 12:37 ` Alexander Kanavin [this message]
2017-04-20 12:56 ` Mark Hatle
2017-04-20 13:04 ` Martin Jansa
2017-04-21 7:55 ` David Vincent
-- strict thread matches above, loose matches on Subject: below --
2017-03-06 8:49 David Vincent
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=d67f6cb5-482e-9e3f-bde5-4284e8eeb31b@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=freesilicon@gmail.com \
--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