From: Patrick Ohly <patrick.ohly@intel.com>
To: Mark Asselstine <mark.asselstine@windriver.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-webserver][PATCH] meta-webserver: apache2 allow SYSTEMD_AUTO_ENABLE to be overwritten
Date: Thu, 16 Nov 2017 23:14:02 +0100 [thread overview]
Message-ID: <1510870442.5979.36.camel@intel.com> (raw)
In-Reply-To: <1822334.tYZlPLg4XR@yow-masselst-lx1>
On Thu, 2017-11-16 at 15:00 -0500, Mark Asselstine wrote:
> On Thursday, November 16, 2017 7:28:06 PM EST Patrick Ohly wrote:
> > On Thu, 2017-11-16 at 10:19 -0500, Mark Asselstine wrote:
> > > The current assignment does not allow a bbappend to be used to
> > > overwrite the SYSTEMD_AUTO_ENABLE value in order to have apache2
> > > auto
> > > start.
> >
> > Why does SYSTEMD_AUTO_ENABLE_${PN} = "enable" in a apache2_*.bb not
> > work? It works fine for me with wpa-supplicant:
>
> Sorry. You are correct the bbappend will overwrite it, but this
> requires a bbappend. If this used "?=" you could achieve this in a
> local.conf or similar.
SYSTEMD_AUTO_ENABLE_pn-wpa-supplicant = "enable" in local.conf also
overrides the = assignment in the .bb file.
> In general if there is a possibility for a value to be desireable to
> overwrite using "?=" makes sense. Thoughts?
I thought the same for a while, but since then I've come around to the
interpretation that for recipe-specific variables, using =? is mostly
just a cosmetic thing. I can't think of a good example where it really
matters in practice.
It's different for global variables which might get set prior to
parsing a recipe (distro config, local.conf). There it makes sense to
not overwrite a potentially existing value.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-11-16 22:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 15:19 [meta-webserver][PATCH] meta-webserver: apache2 allow SYSTEMD_AUTO_ENABLE to be overwritten Mark Asselstine
2017-11-16 18:28 ` Patrick Ohly
2017-11-16 20:00 ` Mark Asselstine
2017-11-16 22:14 ` Patrick Ohly [this message]
2017-11-20 23:02 ` Mark Asselstine
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=1510870442.5979.36.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=mark.asselstine@windriver.com \
--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.