All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Barker <paul@betafive.co.uk>
To: "Andreas Müller" <schnitzeltony@gmail.com>,
	"Adrian Bunk" <bunk@stusta.de>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH] vlc: rework qt PACKAGECONFIG
Date: Tue, 23 Apr 2019 13:07:21 +0100	[thread overview]
Message-ID: <ba049a6b-31ad-7bbf-3759-87a43f3d3d30@betafive.co.uk> (raw)
In-Reply-To: <CALbNGRQ1Va=0Yn_s17mnr6YeL1V0oNFViFZzeAf1184=WtW1gg@mail.gmail.com>

On 23/04/2019 12:30, Andreas Müller wrote:
> On Tue, Apr 23, 2019 at 8:08 AM Adrian Bunk <bunk@stusta.de> wrote:
>>>> Perhaps we should have qt5 as a distro feature instead?
>>> Isn't that a different naming for the same thing not working properly
>>> if you don't have meta-qt5 in layers?
>>
>> Isn't this a reason for moving vlc out of meta-openembedded?
>> Or alternatively moving qt5 to meta-openembedded.
>>
>>> Andreas
>>
>> cu
>> Adrian
> This discussion turns into the same direction as seen before on other occasions:
> 
> My priority is building images where things work out of the box and it
> seems this expectation is not common here. There are several default
> configurations around reducing things down to death to save build time
> and make yocto script happy. I disagree completely but won't discuss
> further. So I will
> 
> * send V3 of this patch not enabling qt5 if meta-qt5 is in layers
> * add a bbappend to my meta-mortsgna because that's what distro layers are for
> 
> Andreas
> 

The issue here is the different 'out of the box' situations Yocto needs 
to support. Some of the boards I've deployed images on have 16MB flash 
for the rootfs (with a greatly reduced write speed to the volume due to 
hardware bugs), others currently have a 16GB SD card in them.

Distro layers are the right place for making cut off decisions on the 
minimum you'll support. A distro config that produces 'out of the box' 
working images for a subset of the boards Yocto Project supports is 
definitely a good thing to have.

Thanks,

-- 
Paul Barker
Managing Director & Principal Engineer
Beta Five Ltd


  reply	other threads:[~2019-04-23 12:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-22 23:46 [PATCH] vlc: rework qt PACKAGECONFIG Andreas Müller
2019-04-22 23:55 ` Paul Barker
2019-04-23  0:07   ` Andreas Müller
2019-04-23  0:41     ` Paul Barker
2019-04-23  6:08     ` Adrian Bunk
2019-04-23 11:30       ` Andreas Müller
2019-04-23 12:07         ` Paul Barker [this message]
2019-04-23 12:19         ` Adrian Bunk
2019-04-23 11:55 Andreas Müller

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=ba049a6b-31ad-7bbf-3759-87a43f3d3d30@betafive.co.uk \
    --to=paul@betafive.co.uk \
    --cc=bunk@stusta.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=schnitzeltony@gmail.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.