FS#23929 - [tcp_wrappers] Remove from official repos.

Attached to Project: Arch Linux
Opened by Kristoffer Tidemann (ktide) - Monday, 25 April 2011, 11:44 GMT
Last edited by Eric Belanger (Snowman) - Wednesday, 27 July 2011, 03:41 GMT
Task Type Feature Request
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Reasons:

1) Inconsistent. Not every package that does relevant networking supports/uses it.
2) The user can and should not rely on libwrap due to 1) which may or may not force him to use something superior in addition to libwrap to offset it's inconsistency thus making it obsolete.
3) We use it by default, this just feels wrong.
This task depends upon

Closed by  Eric Belanger (Snowman)
Wednesday, 27 July 2011, 03:41 GMT
Reason for closing:  Implemented
Comment by Greg (dolby) - Monday, 25 April 2011, 12:30 GMT
Its been brought up twice on arch-dev-public:
http://mailman.archlinux.org/pipermail/arch-dev-public/2010-September/017872.html
http://mailman.archlinux.org/pipermail/arch-dev-public/2010-December/018754.html
If its possible and it doesnt cause any regresssions you have my vote.

"can all these applications be built without tcp_wrappers support?"
List of applications linking to libwrap: http://mailman.archlinux.org/pipermail/arch-dev-public/2010-December/018756.html
"Are there any other distributions that do not use tcp wrappers at all?"
Comment by Kristoffer Tidemann (ktide) - Monday, 25 April 2011, 12:44 GMT
I think Slackware uses it but nothing else comes to mind.

Edit: Debian apparently. http://qa.debian.org/popcon.php?package=tcp-wrappers

Mostly libwrap has to be specifically enabled via ./configure. Have to weed trough the PKGBUILDs
Comment by Greg (dolby) - Monday, 25 April 2011, 12:51 GMT

Loading...