Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2018-02-25
Date: Mon, 26 Feb 2018 20:01:38 +0100	[thread overview]
Message-ID: <877eqzshgt.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180226154724.4e87f072@windsurf.lan> (Thomas Petazzoni's message of "Mon, 26 Feb 2018 15:47:24 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

 > Hello,
 > On Mon, 26 Feb 2018 15:06:20 +0100, Peter Korsgaard wrote:

 >> > mplayer upstream is dead ? If that is the case, then indeed we should
 >> > just take those patches as-is.  
 >> 
 >> I haven't followed development in details, but the latest mplayer
 >> release is more than 2 years old and several forks exists (E.G. mpv).

 > But isn't mplayer one of those projects that says that releases are
 > useless, and people should always use the latest trunk/master/tip
 > because it's obviously "the best".

Maybe. I do see some recent changes in subversion, but mainly small
things (tweaks to the handwritten configure script).

 >> >> Or deprecate qt4?  
 >> 
 >> > Just because it's broken on powerpc?  
 >> 
 >> Well, mainly because it is no longer maintained upstream. Even Debian is
 >> removing Qt4:
 >> 
 >> https://wiki.debian.org/Qt4Removal

 > True, but we are not going to remove it for 2018.02, right ?

It is indeed getting quite late for 2018.02, but given that:

- It isn't supported upstream
- The package is orphaned in Buildroot
- Other distributions (like Debian) no longer supports it

Makes me think that we won't be able to do a good job supporting it
throughout the 2018.02 support cycle.

We don't have a good way of handling deprecations, so I'm not sure what
the best option is:

- Do nothing
- Change prompt to "Qt (obsolete)"
- Remove package

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2018-02-26 19:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26  7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-02-25 Thomas Petazzoni
2018-02-26 10:33 ` [Buildroot] Analysis of build " Thomas Petazzoni
2018-02-26 10:51   ` Johan Oudinet
2018-02-26 10:58     ` Thomas Petazzoni
2018-02-26 13:44     ` Frank Hunleth
2018-02-26 12:48   ` Peter Korsgaard
2018-02-26 13:00     ` Thomas Petazzoni
2018-02-26 14:06       ` Peter Korsgaard
2018-02-26 14:47         ` Thomas Petazzoni
2018-02-26 19:01           ` Peter Korsgaard [this message]
2018-03-01 19:41             ` Arnout Vandecappelle
2018-03-01 21:17               ` Peter Korsgaard
2018-02-27 12:08     ` Peter Seiderer
2018-02-27 13:12       ` Peter Korsgaard
2018-02-26 15:30   ` Mahyar Koshkouei
2018-02-26 15:40     ` 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=877eqzshgt.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