All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Müller" <schnitzeltony@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Mark Asselstine <mark.asselstine@windriver.com>,
	openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-xfce][PATCH] xfce4-panel: fix QA issue 'installed-vs-shipped'
Date: Tue, 19 Jun 2018 00:27:43 +0200	[thread overview]
Message-ID: <CALbNGRRK=096t=CpWX21Sk8aHTFD7Vtbmt2L1pO-A5CVo-8Rng@mail.gmail.com> (raw)
In-Reply-To: <1f9bbaf400d215f993042b2fd2b24342aff1b29f.camel@linuxfoundation.org>

On Mon, Jun 18, 2018 at 11:42 PM, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
Off-Topic / FYI for me gmail considered your email spam
>
> Removing the libtool files became the project default a while ago (Jan
> 2017):
>
> meta/conf/distro/defaultsetup.conf:INHERIT_DISTRO ?= "debian devshell sstate license remove-libtool"
>
> so I suspect you're in the minority not using that now.
Maybe true. But breaking builds consumes resources on many sides -
this thread is a good example
>
> http://git.yoctoproject.org/cgit.cgi/poky/commit/meta/conf/distro/defaultsetup.conf?id=3e2a47fdfceccd5f8832235b7a2df83076e84a98
>
The more I think about this:

* Why is remove-libtool something a distro can override? If causing
trouble it can be deactivated recipe-wise.
  - or
* does anybody see a problem with inherit remove-libtool for all xfce
recipes in xfce.bbclass?

Andreas


  reply	other threads:[~2018-06-18 22:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18 14:45 [meta-xfce][PATCH] xfce4-panel: fix QA issue 'installed-vs-shipped' Mark Asselstine
2018-06-18 16:51 ` Andreas Müller
2018-06-18 17:07   ` Mark Asselstine
2018-06-18 17:15     ` Mark Asselstine
2018-06-18 17:48       ` Mark Asselstine
2018-06-18 17:50         ` Khem Raj
2018-06-18 17:54           ` Mark Hatle
2018-06-18 17:57             ` Khem Raj
2018-06-18 18:09               ` Mark Asselstine
2018-06-18 18:47                 ` Khem Raj
2018-06-18 18:55                   ` Mark Hatle
2018-06-18 20:10                     ` Andreas Müller
2018-06-18 20:14                       ` Mark Asselstine
2018-06-18 20:22                         ` Andreas Müller
2018-06-18 20:27                     ` Khem Raj
2018-06-18 21:42     ` Richard Purdie
2018-06-18 22:27       ` Andreas Müller [this message]
2018-06-18 23:25         ` Mark Asselstine
2018-06-18 23:40           ` Khem Raj
2018-06-19  9:53           ` Richard Purdie
2018-06-19 14:43             ` Khem Raj

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='CALbNGRRK=096t=CpWX21Sk8aHTFD7Vtbmt2L1pO-A5CVo-8Rng@mail.gmail.com' \
    --to=schnitzeltony@gmail.com \
    --cc=mark.asselstine@windriver.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 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.