From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: David Vincent <freesilicon@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] openssl: Fix symlink creation
Date: Wed, 19 Apr 2017 15:56:08 +0300 [thread overview]
Message-ID: <bc76e312-73dd-65bc-37f1-e529f8d311ad@linux.intel.com> (raw)
In-Reply-To: <64f205a9-74d2-1161-14f1-5ed03298f350@linux.intel.com>
On 04/19/2017 02:57 PM, Alexander Kanavin wrote:
> On 04/19/2017 02:53 PM, David Vincent wrote:
>
>>> This kind of thing is better done via ROOTFS_POSTPROCESS_COMMAND, I
>>> think. Look for examples in rootfs-postcommands.bbclass.
>>
>> The problem of ROOTFS_POSTPROCESS_COMMAND is that it is a one shot
>> function
>> that is run at image creation. In my case, I must be able to upgrade the
>> package over time via package management tools. Sorry for not bringing
>> that up
>> before.
>
> What is it in the openssl config file that must be managed via package
> updates?
I mean, if you need to perform a customization to openssl.cnf, why not
patch it in the source tree via openssl.bbappend?
Alex
next prev parent reply other threads:[~2017-04-19 12:56 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 [this message]
2017-04-19 13:03 ` David Vincent
2017-04-20 12:37 ` Alexander Kanavin
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=bc76e312-73dd-65bc-37f1-e529f8d311ad@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 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.