From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Matthew McClintock <msm@freescale.com>,
openembedded-core@lists.openembedded.org
Subject: Re: File conflicts between PN-doc packages
Date: Fri, 25 Jan 2013 14:35:21 +0000 [thread overview]
Message-ID: <1359124521.13917.4.camel@ted> (raw)
In-Reply-To: <20130125142322.GH3200@jama>
On Fri, 2013-01-25 at 15:23 +0100, Martin Jansa wrote:
> On Thu, Jan 24, 2013 at 12:41:19AM +0000, Richard Purdie wrote:
> > On Wed, 2013-01-23 at 18:33 -0600, Mark Hatle wrote:
> > > On 1/23/13 6:13 PM, Chris Larson wrote:
> > > >
> > > > On Wed, Jan 23, 2013 at 10:27 AM, Martin Jansa <martin.jansa@gmail.com
> > > > <mailto:martin.jansa@gmail.com>> wrote:
> > > >
> > > > | * check_data_file_clashes: Package gcc-doc wants to install file
> > > > rootfs/usr/share/info/dir
> > >
> > > I missed this earlier. Yes, the 'dir' file in an info (-doc) package should not
> > > be included. It's existence is an error. This might be a sanity check we
> > > should be adding.
>
> Good to see that world-image is useful to detect other kinds of issues
> then I originally expected :).
>
> > autotools_do_install() in autotools.bbclass actually purges those.
> > Whether it should be autotools or the base class I'm not so sure but it
> > was a common problem for autotools recipes...
>
> It's removed in gcc-configure-runtime.inc but only for libgomp
> RUNTIMETARGET, does someone remember why? Adding Matthew, because that
> removal was added in:
Its safe to remove in all cases. Its basically an index so if we care
about it, we should generate it on target at image build time.
Cheers,
Richard
prev parent reply other threads:[~2013-01-25 14:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 17:27 File conflicts between PN-doc packages Martin Jansa
2013-01-24 0:13 ` Chris Larson
2013-01-24 0:33 ` Mark Hatle
2013-01-24 0:41 ` Richard Purdie
2013-01-25 14:23 ` Martin Jansa
2013-01-25 14:35 ` Richard Purdie [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=1359124521.13917.4.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=msm@freescale.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