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 17:09:33 +0200	[thread overview]
Message-ID: <20150826170933.4501e3e8@free-electrons.com> (raw)
In-Reply-To: <87vbc3xgcq.fsf@dell.be.48ers.dk>

Peter,

On Tue, 25 Aug 2015 22:28:37 +0200, Peter Korsgaard wrote:
> >>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
> 
> Hi,
> 
>  >  I'm not going to comment on all the points made here, but my stance
>  > is: lthough I also hate what the wf111 package does, I don't think
>  > it's bad enough to remove it from buildroot. It doesn't hurt the rest
>  > of buildroot at all, and it is a useful package for some users. I'd
>  > rather get rid of sparc than getting rid of this package.
> 
> I'm with Arnout here. While the download/binary blobs issues certainly
> aren't nice (and perhaps we would have had second thoughts when it was
> submitted if we had known about these issues)

From the commit log of the package:

    Adds support for the BlueGiga WF111 WiFi driver and the binary utilities
    distributed alongside the driver. An account is required to download the
    sources from the BlueGiga website, which can be created freely. The
    driver is available for armv5, arm7a and i386.
    
    Since it is not possible to automatically retrieve the sources, because
    of the required user account needed on the BlueGiga website, an option
    is added to let the Buildroot user specify the directory where the
    driver tarball was downloaded.

So it was 100% clear when the package was submitted that the tarball
cannot be automatically retrieved, and that creating an account was
needed to download the tarball.

See also the initial package submission:

    http://lists.busybox.net/pipermail/buildroot/2015-January/118194.html

Best regards,

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

  reply	other threads:[~2015-08-26 15:09 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 [this message]
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

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=20150826170933.4501e3e8@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