Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] insane.bbclass: Added QA warning for shipping /usr/share/info/dir
Date: Wed, 10 Jul 2013 13:44:05 +0200	[thread overview]
Message-ID: <20130710114405.GZ3288@jama> (raw)
In-Reply-To: <CAJTo0LbWDHqUoaks86RrGMSnKyN+fw-cxShpFpr=DT-sOGbvxQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 980 bytes --]

On Mon, Jul 01, 2013 at 03:51:26PM +0100, Burton, Ross wrote:
> On 1 July 2013 11:31, Mihai Prica <mihai.prica@intel.com> wrote:
> > /usr/share/info/dir should be generated at install time in a postinst.
> > Added QA warning to check at build time for this file. The warning
> > is disabled by default.
> 
> Patch is good but why don't we enable this by default?

FWIW: this is list of QA issues found with this check in my world builds:

gcc-4.8.1: The /usr/share/info/dir file is not meant to be shipped in a particular package.
ed-1.7: The /usr/share/info/dir file is not meant to be shipped in a particular package.
emacs-23.4: The /usr/share/info/dir file is not meant to be shipped in a particular package.
quagga-0.99.21: The /usr/share/info/dir file is not meant to be shipped in a particular package.
lzip-1.14: The /usr/share/info/dir file is not meant to be shipped in a particular package.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2013-07-10 11:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01 10:30 [PATCH 0/1] insane.bbclass: Added QA warning for shipping /usr/share/info/dir Mihai Prica
2013-07-01 10:31 ` [PATCH 1/1] " Mihai Prica
2013-07-01 14:51   ` Burton, Ross
2013-07-10 11:44     ` Martin Jansa [this message]
2013-07-11  7:15       ` Prica, Mihai

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=20130710114405.GZ3288@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox