From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] prelink: Uprev prelink to latest version (V2)
Date: Fri, 24 Jun 2011 23:36:09 -0500 [thread overview]
Message-ID: <4E0565B9.301@windriver.com> (raw)
In-Reply-To: <20110624205136.GB7676@sakrah.homelinux.org>
On 6/24/11 3:51 PM, Khem Raj wrote:
> On (24/06/11 14:42), Mark Hatle wrote:
>> The latest cross-prelink version tracks the prelink r190 SVN.
>>
>> Fix two minor issues as well. If we remove the package, we would
>> unprelink the filesystem after the rm was finished. This is
>> incorrect.. we need to do this prerm.
>>
>> Move the cron and cron configuration file to a new package split.
>> This item is not valid for most embedded users.
>>
>> Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
>> ---
>> .../prelink/prelink/prelink.default | 2 +-
>> meta/recipes-devtools/prelink/prelink_git.bb | 25 +++++++++++++++++--
>> 2 files changed, 23 insertions(+), 4 deletions(-)
>>
>> diff --git a/meta/recipes-devtools/prelink/prelink/prelink.default b/meta/recipes-devtools/prelink/prelink/prelink.default
>> index 901258e..d8802f8 100644
>> --- a/meta/recipes-devtools/prelink/prelink/prelink.default
>> +++ b/meta/recipes-devtools/prelink/prelink/prelink.default
>> @@ -2,7 +2,7 @@
>> # or to yes to enable it.
>> # (if you change this from yes to no prelink -ua
>> # will be run next night to undo prelinking)
>> -PRELINKING=unknown
>> +PRELINKING=yes
>>
>
> this is a functionality change. Will it have system wide effects ?
If the user previously had the prelinker installed onto the target, and had the
cron system installed to run the daily scripts, and never bothered to configure
prelink before.. whenever the script ran it would undo any prelinking that had
occurred.
After the change, it's now optional to install the cron scripts. If they are
installed, they default to -on- which means that if cron runs the script it will
attempt to update the prelinking on the system.
This does not affect the build-time prelinking in any way. For many systems
there is no reason to have the prelinker on the target, it's only needed for
field upgrades.
So, I consider this an enhancement (splitting the script out to make it
optional), and a bug-fix -- enabling re-prelink functionality if the script is
installed -- vs the previous "un-prelink" being the default.
--Mark
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
prev parent reply other threads:[~2011-06-25 4:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 19:42 [PATCH 0/1] Uprev prelink (v2) Mark Hatle
2011-06-24 19:42 ` [PATCH 1/1] prelink: Uprev prelink to latest version (V2) Mark Hatle
2011-06-24 20:51 ` Khem Raj
2011-06-25 4:36 ` Mark Hatle [this message]
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=4E0565B9.301@windriver.com \
--to=mark.hatle@windriver.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