3 ms·
> nobody is working on them as a core part of the OS. If they were in ports and just kinda stuck around due to inertia, that'd make sense I mean, that's exactl
by loeg 9y ago
> nobody is working on them as a core part of the OS. If they were in ports and just kinda stuck around due to inertia, that'd make sense
I mean, that's exactly what happened.
It's like if they were just old unmaintained programs in GNU coreutils. No one maintains them, no one uses them, but they keep getting included until a good argument is made to remove them.
Previous efforts to remove them were probably greeted with "well, someone might still use these tools." And placing them in ports is a little bit of work.
As you say, they were mostly harmless to keep.
- JdeBP 9y agoAs I have said elsewhere on this page, there´s an easy litmus test for who has actually read the headlined message. Those people are not asking the "But but but rsync?" questions; are talking about "ruptime" and "rwho" as well; know exactly where in the source tree the manual pages are, because the headlined message is a patch that gives their pathnames; and are not basing their arguments on the idea that these are not in ports, given what the deprecation notice explicitly says. * https://reviews.freebsd.org/D11345 https://reviews.freebsd.org/D11345
- loeg 9y agoI think you meant to reply to a different comment. None of that is relevant here.