From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/wf111: remove package
Date: Thu, 27 Aug 2015 00:05:27 +0200 [thread overview]
Message-ID: <20150826220527.GB1934@free.fr> (raw)
In-Reply-To: <87zj1dx0g0.fsf@dell.be.48ers.dk>
Peter, All,
On 2015-08-26 22:24 +0200, Peter Korsgaard spake thusly:
> >>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> > Yes, it's a pity we can't get the Qt non-free packages. But especially
> > with Qt, they are such a critical piece of a project that I would not
> > want we tell users hat we have such support in Buildroot. That would
> > just be blatantly lying.
>
> > OTOH, *one* way to which I *may* agree is to add something like
>
> > In Build options ---> Advanced --->
>
> > config UNSUPORTED_NON_PUBLIC_PACKAGES
> > bool "Show unsupported non-public packages"
> > help
> > Some packages do not have publicly accessible source
> > code, either require registration, manual download...
>
> > Buildroot has recipes for building those packages, but
> > given that their sources ar enot freely available, there
> > is not guarantee they do work as expected, not even build
> > at all.
>
> > Use at your own risk. Do not report problems to the
> > Buildroot developpers. Sending patches to fix them might
> > be accepted.
>
> Another alternative is that somebody maintains a set of BR2_EXTERNAL
> packages for this kind of stuff. I'm not sure what the best solution is,
> perhaps this is something to discuss during the dev days?
Yes, that would be an option. We could provide those extra packages as a
br2-external tree.
But then, given the current state of br2-external, if a user wants to
use those packages, he can no longer provide his own br2-external tree.
Or he'd have to manage his customisations in branches in that tree,
which gets him back to square one, that is, not being able to manage
location customisations (local configs, local packages...) in a
completely separate tree.
*But* there is hope!
I do have a series that adds support for using multiple br2-external
trees at once. And your proposal above is just one more excuse for me
to push for that series to be applied!
My evil plan is coming to fruition! :-]
Muhahaha!
https://www.youtube.com/watch?v=ulEAMKhemx8
/me is adding these to the topics for the next DevDays.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2015-08-26 22:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-22 0:13 [Buildroot] [PATCH] package/wf111: remove package Yann E. MORIN
2015-08-23 14:36 ` Thomas Petazzoni
2015-08-23 15:37 ` Yann E. MORIN
2015-08-23 18:58 ` Thomas Petazzoni
2015-08-24 20:07 ` Arnout Vandecappelle
2015-08-24 22:15 ` Floris Bos
2015-08-25 20:28 ` Peter Korsgaard
2015-08-26 15:09 ` Thomas Petazzoni
2015-08-26 15:31 ` Peter Korsgaard
2015-08-26 17:32 ` Thomas Petazzoni
2015-08-26 18:47 ` Yann E. MORIN
2015-08-26 20:24 ` Peter Korsgaard
2015-08-26 22:05 ` Yann E. MORIN [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=20150826220527.GB1934@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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