All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] classes/package: clarify installed-vs-shipped message
Date: Mon, 13 Apr 2015 19:02:13 +0200	[thread overview]
Message-ID: <20150413170213.GK2330@jama> (raw)
In-Reply-To: <2445584.6Z3eITqUyt@peggleto-mobl.ger.corp.intel.com>

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

On Mon, Apr 13, 2015 at 05:46:03PM +0100, Paul Eggleton wrote:
> On Monday 13 April 2015 18:28:28 Martin Jansa wrote:
> > On Mon, Apr 13, 2015 at 04:44:52PM +0100, Paul Eggleton wrote:
> > > Based on the number of times I've had to explain it over the years it
> > > seems that a lot of new users don't immediately realise what is meant
> > > by "shipped" here (nor should we expect them to) so let's at least
> > > mention packaging and briefly tell the user what they need to do. (I was
> > > going to go into more detail in the message, but there is really more
> > > detail than can be covered succinctly here.)
> > > 
> > > Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> > > ---
> > > 
> > >  meta/classes/package.bbclass | 3 ++-
> > >  1 file changed, 2 insertions(+), 1 deletion(-)
> > > 
> > > diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
> > > index 5558d0d..9790e9d 100644
> > > --- a/meta/classes/package.bbclass
> > > +++ b/meta/classes/package.bbclass
> > > @@ -1132,12 +1132,13 @@ python populate_packages () {
> > > 
> > >                  unshipped.append(path)
> > >      
> > >      if unshipped != []:
> > > -        msg = pn + ": Files/directories were installed but not shipped"
> > > +        msg = pn + ": Files/directories were installed but not shipped in
> > > any package:"> 
> > >          if "installed-vs-shipped" in (d.getVar('INSANE_SKIP_' + pn, True) 
> or "").split():
> > >              bb.note("Package %s skipping QA tests: installed-vs-shipped"
> > >              % pn)
> > >          
> > >          else:
> > >              for f in unshipped:
> > >                  msg = msg + "\n  " + f
> > > 
> > > +            msg = msg + "\nPlease either set FILES such that these items
> > > are packaged, or alternatively delete them within do_install"
> > We should also mention the possibility to fix Makefile.am,
> > CMakeLists.txt, ... not to install them in first place.
> 
> This is the sort of thing I was alluding to in the commit message, I'd rather 
> not get into too many specifics, or the message is going to end up very long 
> indeed covering all of the things you need to pay attention to. That kind of 
> thing is much better covered in the documentation.

OK, maybe I'm too sensitive for this, because recently I was fixing few
recipes where do_install task was doing
cp -ra ${S} ${D}
and then INSANE_SKIP was used to ignore "patches" and ".pc" files
"installed" in ${D} but luckily not included in any package.

So I fear that obvious fix after reading this message will be to delete
"patches" and ".pc" directories in do_install instead of fixing the root
cause.

> 
> Cheers,
> Paul
> 
> -- 
> 
> Paul Eggleton
> Intel Open Source Technology Centre

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

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

  reply	other threads:[~2015-04-13 17:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 15:44 [PATCH 0/2] A couple of package-related fixes Paul Eggleton
2015-04-13 15:44 ` [PATCH 1/2] classes/package: clarify installed-vs-shipped message Paul Eggleton
2015-04-13 16:28   ` Martin Jansa
2015-04-13 16:46     ` Paul Eggleton
2015-04-13 17:02       ` Martin Jansa [this message]
2015-04-13 17:52         ` Paul Eggleton
2015-04-13 15:44 ` [PATCH 2/2] lib/oe/package_manager: avoid traceback with no packages Paul Eggleton

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=20150413170213.GK2330@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.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 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.