From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Proposal for dropping some add-ons
Date: Tue, 03 Nov 2020 11:13:37 +0100 [thread overview]
Message-ID: <c8b95d76-4839-5e74-8a70-74ca9fd2271c@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1552 bytes --]
Hello development folks,
while waiting for ${things} to finish here, I went through the Pakfire add-on list
and came across some packages which - as far as I know - ...
(a) ... are not regularly maintained by a member of the IPFire development team
(b) ... do not seem to be frequently installed by our users
(c) ... should not run on a firewall for security purposes, anyway
Among these are:
- Asterisk (13.18.5, upstream is currently on 18.0.0)
- Icinga (1.11.4, upstream is currently on ~ 1.14.2 and 2.x.y, which comes with a bunch of
dependencies such as a database, while Icinga 1.x was more or less a standalone
system)
- libsrtp (1.5.4, upstream is currently on 2.3.0)
- OpenLDAP (2.4.49, upstream is currently on 2.4.55)
- SANE (1.0.28, upstream is currently on 1.0.31, this should not be too hard, but I am not
aware of IPFire users needing this)
- SquidClamAV (since the overwhelming majority of web traffic is encrypted by now, I
guess it makes little sense to ship this add-on anymore. Upstream seems
to be unmaintained - most people are doing this via ICAP those days -,
and this also arises the question why we need ClamAV anymore)
- sslh (1.7a, upstream is currently on 1.21c)
- transmission (2.94, upstream is currently on 3.00, but I do not observe a broader
user group for this)
Are we able to drop those add-ons entirely? If yes, I will submit patches to do so. :-)
Thanks, and best regards,
Peter Müller
next reply other threads:[~2020-11-03 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 10:13 Peter Müller [this message]
2020-11-03 11:03 ` Michael Tremer
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=c8b95d76-4839-5e74-8a70-74ca9fd2271c@ipfire.org \
--to=peter.mueller@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