From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] odroid-mali: mark package as BROKEN
Date: Tue, 07 Mar 2017 16:42:32 +0100 [thread overview]
Message-ID: <87a88xccuv.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170305223726.GM3671@free.fr> (Yann E. MORIN's message of "Sun, 5 Mar 2017 23:37:27 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
>> I'm obviously late with commenting on this, but I think marking things as
>> BROKEN is wrong. It bypasses the legacy mechanism so it disappears without
>> notice. Also, BROKEN packages languish there for years without ever anyone
>> taking a look. Sometimes things do get repaired, but re-adding the package is
>> not much more complicated than
>>
>> So, I propose to remove all broken packages.
> Agreed.
>> [I have the feeling we discussed this kind of thing at some BR devel meeting at
>> some point, but I can't find it.]
> Yes we did. And IIRC we agreed to get rid of BROKEN altogether.
I think you are mixing it up with BR2_DEPRECATED.
With that said, if nobody cares about fixing the package, then I'm OK
with removing it. Lets give it a bit of time and see what happens.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-03-07 15:42 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 [this message]
2017-03-07 17:05 ` Arnout Vandecappelle
2017-03-07 22:56 ` Thomas Petazzoni
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=87a88xccuv.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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