Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Yegor Yefremov <yegorslists@googlemail.com>,
	pieterjanca@gmail.com, brock@cottonwoodcomputer.com
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	 Bernd Kuhls <bernd@kuhls.net>,
	 buildroot@buildroot.org
Subject: Re: [Buildroot] [autobuild.buildroot.org] Daily results for 2026-10-28
Date: Thu, 29 Oct 2026 10:52:44 +0100	[thread overview]
Message-ID: <875wykygsz.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAGm1_kvUUsz4tKbbzn_z6cTSjgBVFjy44yrx5c3c5Y9BUcCPdw@mail.gmail.com> (Yegor Yefremov's message of "Thu, 29 Oct 2026 09:45:12 +0100")

>>>>> "Yegor" == Yegor Yefremov <yegorslists@googlemail.com> writes:

 > Hi All,
 > do we still want to keep the following packages?

 >> madplay-0.15.2b | 1

 > Unmaintained since 2004.

I would say drop it, mpg123 is a better option today.


 >> mender-3.5.3 | 1
 >> mraa-2.2.0 | 1

 > Last release was in 2020. Low git activity.

And Intel Galileo/Edison are dead, maybe indeed drop it?


 >> pdmenu-1.3.6 | 1

 > The last release is from September 2020. git repo shows a very rare activity.

Indeed. It was also dropped from Debian a long time ago, so maybe we
should as well?

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-10-29  9:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29  4:27 [Buildroot] [autobuild.buildroot.org] Daily results for 2026-10-28 Buildroot Notifications
2026-10-29  8:45 ` Yegor Yefremov
2026-10-29  9:52   ` Peter Korsgaard [this message]
2026-10-29 16:04     ` Thomas Petazzoni via buildroot
2026-10-29 20:53       ` Pieterjan Camerlynck

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=875wykygsz.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=bernd@kuhls.net \
    --cc=brock@cottonwoodcomputer.com \
    --cc=buildroot@buildroot.org \
    --cc=pieterjanca@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yegorslists@googlemail.com \
    /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