Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] prelink: Uprev prelink to latest version
Date: Fri, 24 Jun 2011 14:22:20 -0500	[thread overview]
Message-ID: <4E04E3EC.1030604@windriver.com> (raw)
In-Reply-To: <BC8EDE88-C1B5-4991-BE9F-A5D735F81A3B@dominion.thruhere.net>

On 6/24/11 2:18 PM, Koen Kooi wrote:
> 
> Op 24 jun 2011, om 21:10 heeft Mark Hatle het volgende geschreven:
> 
>> 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.
>>
>> Also disable the cron configuration file.  This isn't appropriate
>> for embedded systems, but someone might still find it useful.
>>
>> Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
>> ---
>> meta/recipes-devtools/prelink/prelink_git.bb |   18 +++++++++++++-----
>> 1 files changed, 13 insertions(+), 5 deletions(-)
>>
>> diff --git a/meta/recipes-devtools/prelink/prelink_git.bb b/meta/recipes-devtools/prelink/prelink_git.bb
>> index 1eea30a..044cb6b 100644
>> --- a/meta/recipes-devtools/prelink/prelink_git.bb
>> +++ b/meta/recipes-devtools/prelink/prelink_git.bb
>> @@ -8,9 +8,9 @@ and executables, so that far fewer relocations need to be resolved at \
>> runtime and thus programs come up faster."
>> LICENSE = "GPLv2"
>> LIC_FILES_CHKSUM = "file://COPYING;md5=c93c0550bd3173f4504b2cbd8991e50b"
>> -SRCREV = "909470ee441237563d6236c505cb2d02ddc48704"
>> +SRCREV = "ac461e73b17253a4da25c5aafeac7193b553156c"
>> PV = "1.0+git${SRCPV}"
>> -PR = "r2"
>> +PR = "r3"
>>
>> SRC_URI = "git://git.yoctoproject.org/prelink-cross.git;protocol=git \
>>            file://prelink.conf \
>> @@ -35,11 +35,15 @@ do_configure_prepend () {
>>         echo "all:" > ${S}/doc/Makefile.am
>> }
>>
>> +# Disabled the cron and cron configuration file, isn't appropriate for
>> +# embedded systems.  (The script re-prelinks the system daily -- on
>> +# systems where users are adding applications, this might be reasonable
>> +# but for embedded, we should be re-running prelink -a after an update.)
>> do_install_append () {
>> 	install -d ${D}${sysconfdir}/cron.daily ${D}${sysconfdir}/default ${D}${sysconfdir}/rpm
>> 	install -m 0644 ${WORKDIR}/prelink.conf ${D}${sysconfdir}/prelink.conf
>> -	install -m 0644 ${WORKDIR}/prelink.cron.daily ${D}${sysconfdir}/cron.daily/prelink
>> -	install -m 0644 ${WORKDIR}/prelink.default ${D}${sysconfdir}/default/prelink
>> +#	install -m 0644 ${WORKDIR}/prelink.cron.daily ${D}${sysconfdir}/cron.daily/prelink
>> +#	install -m 0644 ${WORKDIR}/prelink.default ${D}${sysconfdir}/default/prelink
>> 	install -m 0644 ${WORKDIR}/macros.prelink ${D}${sysconfdir}/rpm/macros.prelink
> 
> How about PACKAGES += prelink-cron, FILES_prelink-cron = "{sysconfdir}/cron.dailly" ,etc ,etc ?

I thought about that, but I'm still not sure the stuff is useful.. The default
configuration actually disables prelink and on the next run of cron will
un-prelink your system.

So it's really not useful from what I can tell.  Of course we could easily
change the default to "on" instead of off...  or change the prelink.bbclass to
enable the cron prelink script if it exists....  but as it stands it looks more
broken then useful.

--Mark



      reply	other threads:[~2011-06-24 19:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24 19:10 [PATCH 0/1] Uprev prelink Mark Hatle
2011-06-24 19:10 ` [PATCH 1/1] prelink: Uprev prelink to latest version Mark Hatle
2011-06-24 19:18   ` Koen Kooi
2011-06-24 19:22     ` 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=4E04E3EC.1030604@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