From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Alex Ferguson <thoughtmonster@gmail.com>
Subject: Re: [PATCH] classes: Modify rootfs_ipk.bbclass for -force-overwrite.
Date: Fri, 29 Oct 2010 16:55:36 +0200 [thread overview]
Message-ID: <20101029145536.GA3206@jama> (raw)
In-Reply-To: <1288361334-17427-1-git-send-email-thoughtmonster@gmail.com>
On Fri, Oct 29, 2010 at 05:08:54PM +0300, Alex Ferguson wrote:
> Rationale: In Jlime we ship a package called jlime-extras which
> contains several files (configuration files, scripts, etc.), some
> of which conflict with files provided by other packages. This is
> intentional, and is for distro customization purposes. For example
> we ship a modified version of the /usr/bin/startx script, some
> alternative icons for applications, some modified .desktop files
> and so on. Building an image with this jlime-extras package fails,
> of course, due to conflicting files.
Why not modify the original files in corresponding recipes with distro
override?
Problem with this kind of package overwritting other packages is when
original package is upgraded (PR bump or even just DISTRO_PR) it forces
user to also use -force-overwrite and then he will loose those
customizations.
I don't have problem with it as long as it's conditional, but I would be
very carefull with using it. IMHO this is good only if you're building
images which are not supposed to be upgraded by user with ie opkg on target.
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next prev parent reply other threads:[~2010-10-29 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 14:08 [PATCH] classes: Modify rootfs_ipk.bbclass for -force-overwrite Alex Ferguson
2010-10-29 14:21 ` Eric Bénard
2010-10-29 14:39 ` Graeme Gregory
2010-10-29 14:55 ` Martin Jansa [this message]
2010-10-29 15:40 ` Alex Ferguson
2010-10-29 17:44 ` Khem Raj
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=20101029145536.GA3206@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=thoughtmonster@gmail.com \
/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.