#22920: pureftpd: update, rename to pure-ftpd ------------------------------+--------------------------------------------- Reporter: scott@… | Owner: ryandesign@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 1.8.1 Keywords: | Port: pure-ftpd, pureftpd ------------------------------+--------------------------------------------- Comment(by scott@…): Replying to [comment:1 ryandesign@…]:
We can leave the pureftpd port around as a stub to help people upgrade to pure-ftpd (using the `replaced_by` keyword).
I'm looking through the new portfile now.
If you know how to do that, I did not. I am guessing, you remove the pureftpd Portfile, and it would more or less do nothing, other than tell you to go install something else? I am fine with that. I believe it will be very important that any activated pureftpd ports be backed up, deactivated and then pure-ftpd put in place. It would probably be worse to not change the name, as an upgrade would then be easily possible, leaving a good deal of mess behind. Much like I believe what will make moving Apache2 to a more appropriate location is going to be challenging, this is similar. The name change in this case, makes it easier. -- Ticket URL: <http://trac.macports.org/ticket/22920#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS