All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] odroid-mali: mark package as BROKEN
Date: Tue, 7 Mar 2017 23:56:52 +0100	[thread overview]
Message-ID: <20170307235652.10fefb7b@free-electrons.com> (raw)
In-Reply-To: <bb95fc23-ae23-3f4b-da4c-13bda8aa7e07@mind.be>

Hello,

On Tue, 7 Mar 2017 18:05:02 +0100, Arnout Vandecappelle wrote:

>  The problem with BROKEN is the same as with BR2_LEGACY: it doesn't appear in
> the legacy menu. You could argue that BROKEN is different because it simply
> can't be used at all. However, for the user there is no difference: it used to
> work (I hope we can assume that when a package is added, it has worked at least
> once on at least one platform...), and after a Buildroot update it suddenly
> vanishes.

Agreed. In this specific case, I believe odroid-mali definitely works
for some situations, so there are certainly valid use cases for the
package as it is today, i.e it is not *completely* broken. But it
causes some build failures, which nobody has taken care of, and
upstream is unlikely to be responsive/

>  So I propose the following: we can still mark things as BROKEN as a way to
> motivate people to fix them, but during the RC month we properly remove them and
> add a legacy entry.

Full ACK.

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

  reply	other threads:[~2017-03-07 22:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-04 14:34 [Buildroot] [PATCH] odroid-mali: mark package as BROKEN Thomas Petazzoni
2017-03-05 13:20 ` Yann E. MORIN
2017-03-05 20:37 ` Thomas Petazzoni
2017-03-05 22:33   ` Arnout Vandecappelle
2017-03-05 22:37     ` Yann E. MORIN
2017-03-07 15:42       ` Peter Korsgaard
2017-03-07 17:05         ` Arnout Vandecappelle
2017-03-07 22:56           ` Thomas Petazzoni [this message]
2017-03-08  6:55             ` daggs
2017-03-08  8:02               ` Thomas Petazzoni
2017-03-05 22:40     ` Thomas Petazzoni
2017-03-05 23:35       ` Arnout Vandecappelle
2017-03-06  8:13         ` Thomas Petazzoni

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=20170307235652.10fefb7b@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 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.