All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Laurent Bonnans <laurent.bonnans@hikob.com>,
	"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] python: remove tests and sqlite3-tests modules
Date: Wed, 06 Apr 2016 10:19:54 +0100	[thread overview]
Message-ID: <1459934394.7348.199.camel@linuxfoundation.org> (raw)
In-Reply-To: <CABBNMXVNRa8ANtg9dFgfT1nF8br-hB4_w1Q07FMjq=2Sq+L_RQ@mail.gmail.com>

On Wed, 2016-04-06 at 10:00 +0200, Laurent Bonnans wrote:
> 2016-04-05 16:56 GMT+02:00 Burton, Ross <ross.burton@intel.com>:
> > 
> > On 31 March 2016 at 17:15, Laurent Bonnans <
> > laurent.bonnans@hikob.com>
> > wrote:
> > > 
> > > If present in manifests, they are shipped in 'python-modules'.
> > > This
> > > commit keeps them avalaible in the 'python-misc' package.
> > 
> > 
> > python-modules depends on python-misc, so this won't really achieve
> > anything.
> 
> You're right, I missed the change which adds this dependency in
> master.
> 
> What would then be the best way to avoid shipping tests when using
> python-modules?
> Add another package(s) in the main recipe files before python-misc?

Exclude those packages from python-modules as I previously suggested?

Cheers,

Richard


      reply	other threads:[~2016-04-06  9:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-31 16:15 [PATCH 0/1] python: remove tests and sqlite3-tests modules Laurent Bonnans
2016-03-31 16:15 ` [PATCH 1/1] " Laurent Bonnans
2016-03-31 21:54   ` Richard Purdie
2016-04-01 11:21     ` Laurent Bonnans
2016-04-01 11:42       ` Richard Purdie
2016-04-05 14:56   ` Burton, Ross
2016-04-06  8:00     ` Laurent Bonnans
2016-04-06  9:19       ` 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=1459934394.7348.199.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=laurent.bonnans@hikob.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 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.