Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/wf111: remove package
Date: Wed, 26 Aug 2015 19:32:51 +0200	[thread overview]
Message-ID: <20150826193251.02c382a3@free-electrons.com> (raw)
In-Reply-To: <87bnduxe0t.fsf@dell.be.48ers.dk>

Peter, Yann,

On Wed, 26 Aug 2015 17:31:14 +0200, Peter Korsgaard wrote:

> Yeah, I should probably have been more clear. _I_ didn't notice the issue
> back when it was submitted (and you committed the patch). If I had,
> perhaps I would have commented on it.

The thing is that I'm not sure what we can do about it, or other
packages for which the source/binary is not available in a way that
allows automated downloading (either because creating an account is
needed, or because the program/library is not free). Besides wf111,
another example I gave are the different Qt5 components that are only
available to paying Qt customers.

On the one hand, having the package in the main Buildroot tree makes
things easy for people having access to those components: it's
supported by default in Buildroot.

On the other hand however, since we, maintainers and core developers of
Buildroot, may not have access to those components, it might be
problematic for long term testing and maintenance.

I'm not really sure how to solve this situation. Should we reject all
such packages and ask people to keep them in their private trees (which
limits a lot the sharing of such packages: the whole point of Buildroot
as an open-source project is to share as many package recipes as
possible). Or should we integrate them, maybe marking them in a special
way that indicates that we can't test/maintain them?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-08-26 17:32 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 [this message]
2015-08-26 18:47                 ` Yann E. MORIN
2015-08-26 20:24                   ` Peter Korsgaard
2015-08-26 22:05                     ` Yann E. MORIN

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=20150826193251.02c382a3@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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