From: Rob Kramer <robk@starhub.net.sg>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Custom handling of ipk upgrade conflicts..
Date: Wed, 25 Nov 2009 14:36:32 +0800 [thread overview]
Message-ID: <heijcd$lme$1@ger.gmane.org> (raw)
In-Reply-To: 6ec4247d0911240311x4e758d1ctd6a0295b10510aa6@mail.gmail.com
Graham Gower wrote:
> It sounds like something that a preinst script would be suited to.
>
> Could you elaborate on the custom merging that you wish to do?
For example, it could merge setting entries in a config file with a new file
from the ipk package. Or decide not to install the file at all, if there
already is a file that is 'good enough' (i.e. passes some custom testing).
Cheers,
Rob
prev parent reply other threads:[~2009-11-25 6:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 9:12 Custom handling of ipk upgrade conflicts Rob Kramer
2009-11-24 11:11 ` Graham Gower
2009-11-25 6:36 ` Rob Kramer [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='heijcd$lme$1@ger.gmane.org' \
--to=robk@starhub.net.sg \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox