#22920: pureftpd: update, rename to pure-ftpd ----------------------------------+----------------------------------------- Reporter: scott@… | Owner: ryandesign@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.8.1 Resolution: fixed | Keywords: Port: pure-ftpd, pureftpd | ----------------------------------+----------------------------------------- Comment(by ryandesign@…): Replying to [comment:9 scott@…]:
Id 4 spaces per tabs a "best practices" issue in MacPorts? I really do not care one way or the other.
Yeah, it's how most other ports do it, and it's [http://guide.macports.org/#development.practices.portstyle in the guide].
@PREFIX@ ah ha, so that is how that is done, thank you!
Yes, you just put some string into the file that wouldn't otherwise occur, then reinplace it. I use "@PREFIX@", I've seen others use "@@PREFIX@@" or "!__PREFIX" or "MACPORTS_PREFIX" or similar. Doesn't matter what it is, as long as it's not already in the file.
Thanks on the port-destroot create dirs changes, I was not aware of how to do that, so I did the best I knew at the time.
This way, the directories essentially also get registered to the port, so they disappear when the port is uninstalled -- if they're empty, that is.
And thanks again on the openssl "depends_lib-append port:openssl " changes. I guess I had that in place, so it never bothered me.
The port had that line in it before your changes, but yeah, there were several reasons it needed to be changed.
Sounds like a good idea for me to set up a second prefix, one I use for working in, and one I use for developing in, that was I would have caught all of these. Any new port, I can `sudo -df port uninstall all` on the secondary prefix, and then try to install just my one port, with all variants. Is that the suggested method to come out with more rock solid port submissions?
That sounds time-consuming and complicated. :) I don't go to that much effort myself. Ports don't have to be perfect either. I just fixed the things I noticed. If I missed them, someone else might've seen them later, and filed a bug report, and it could be fixed then. -- Ticket URL: <http://trac.macports.org/ticket/22920#comment:10> MacPorts <http://www.macports.org/> Ports system for Mac OS