Tired of dupes of Bug 159747; the rp-pppoe thing been deprecated in baselayout for ages in favour of ppp and if people want a fancy icon, they can use kppp. Any good reason why this stuff shouldn't be removed?
I don't mind removing rp-pppoe, but rppppoek is actually independent of this: rpppoek is a very lightweight application which essentially only calls the /usr/bin/rppppoek.sh script which in turn can easily be customized e.g. to run /etc/init.d/net.ppp0 start/stop or something similar (this is very convenient to install on computers for people who are afraid of a shell). I cannot see how kppp could easily replace this. So why remove rpppoek.sh from the tree without any need? Removing the rp-pppoe dependency (and perhaps providing a different rpppoek.sh default script) would be enough...
I'm strictly against removal of rp-pppoe since it's offers not only the client but server for PPPoE. There are strong evidences that pppoe-server is really used in many environments such as small campus networks and home servers.
*** Bug 204476 has been marked as a duplicate of this bug. ***
It's amazing that bug 159747 still make its victims! How often do these guys make their updates? And how come the 3.8-r1 revbump didn't fixed their problem? Anyway, rp-pppoe cannot be removed because a) it is the only PPPoE server software we have (as pointed out by Aleksey) and b) apparently it is easier to use by Joe Average. rppppoek is a simple KDE applet that control rp-pppoe client connection. It cannot be modified to run net.pppX script simple because it will require root privileges for that. I agree it could be replaced by kppp, but that would require a knowledgeable user, one who would know what pppd parameters are needed for running a PPPoE client connection. Basically there are 2 types of PPPoE users: a) one who would prefer to set their connection through init scripts and therefore use baselayout for that. b) the other who would prefer to control their connection Windows style, through applets. For them, rppppoek or (for peeps that knows a thing or two about PPP) kppp is the answer. In conclusion, none of these packages can be removed. However, you could ask baselayout peeps to remove rp-pppoe support as obsolete. Closed as INVALID.
(In reply to comment #4) > It's amazing that bug 159747 still make its victims! How often do these guys > make their updates? And how come the 3.8-r1 revbump didn't fixed their problem? NFC really... > However, you could ask baselayout peeps to remove rp-pppoe support as > obsolete. Sounds like a plan, I'll poke uberlord about this. Thanks. ;)
