From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: File conflicts between PN-doc packages
Date: Thu, 24 Jan 2013 00:41:19 +0000 [thread overview]
Message-ID: <1358988079.3616.6.camel@ted> (raw)
In-Reply-To: <51008153.6090800@windriver.com>
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.
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...
Cheers,
Richard
next prev parent reply other threads:[~2013-01-24 0:57 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 [this message]
2013-01-25 14:23 ` Martin Jansa
2013-01-25 14:35 ` Richard Purdie
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=1358988079.3616.6.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=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