From: Arne Fitzenreiter <arne_f@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Drop unused/unmaintained packages
Date: Sat, 15 Feb 2020 18:49:03 +0100 [thread overview]
Message-ID: <a9c47d0044c8c6a6102fa3c33cb9f09a@ipfire.org> (raw)
In-Reply-To: <20200212093453.5732-1-michael.tremer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
I have not dropped the i2c_tools and w_scan yet.
i2c_tools is nice to debug temperature sensors and for
checking if the i2c busses are working.
w_scan is used for scanning DVB-T channels and we have
working replacement yet.
Arne
Am 2020-02-12 10:34, schrieb Michael Tremer:
> Hello everyone,
>
> I would like to propose to drop the following packages.
>
> They are either not maintained upstream any more, not used by virtually
> anyone, or they are already broken and do not build anyways.
>
> I see a big danger here when we ship software that is dangerously
> broken. Of that, we have much more in the distribution and potentially
> we might drop it, too.
>
> If you have previously worked on a package or even submitted
> that package and want it to remain a part of IPFire, please
> check if any updates are available from upstream and submit
> patches. Otherwise there is a higher chance that your package
> is being dropped, too.
>
> We have only limited resources right now and would like to work
> on things that have a large impact on all users. Maintaining,
> patching and fixing outdated software where even maintainers have
> given up is time-consuming and benefits very few people.
>
> Please see these patches as a proposal. Feel free to disagree
> and become a maintainer for those packages.
>
> Best,
> -Michael
prev parent reply other threads:[~2020-02-15 17:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 9:34 Michael Tremer
2020-02-12 9:34 ` [PATCH 01/14] Drop arm Michael Tremer
2020-02-12 9:34 ` [PATCH 02/14] Drop batctl Michael Tremer
2020-02-12 9:34 ` [PATCH 03/14] Drop multicat & bitstream Michael Tremer
2020-02-12 9:34 ` [PATCH 04/14] Drop check_mk_agent Michael Tremer
2020-02-12 9:34 ` [PATCH 05/14] Drop DirectFB Michael Tremer
2020-02-12 9:34 ` [PATCH 06/14] Drop ez-ipupdate Michael Tremer
2020-02-12 9:34 ` [PATCH 07/14] Drop i2c-tools Michael Tremer
2020-02-12 9:34 ` [PATCH 08/14] Drop icecast Michael Tremer
2020-02-12 9:34 ` [PATCH 09/14] Drop icegenerator Michael Tremer
2020-02-12 9:34 ` [PATCH 10/14] Drop rtpproxy Michael Tremer
2020-02-12 9:34 ` [PATCH 11/14] Drop setserial Michael Tremer
2020-02-12 9:34 ` [PATCH 12/14] Drop streamripper Michael Tremer
2020-02-12 9:34 ` [PATCH 13/14] Drop VDR Michael Tremer
2020-02-12 9:34 ` [PATCH 14/14] Drop w_scan Michael Tremer
2020-02-15 17:49 ` Arne Fitzenreiter [this message]
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=a9c47d0044c8c6a6102fa3c33cb9f09a@ipfire.org \
--to=arne_f@ipfire.org \
--cc=development@lists.ipfire.org \
/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