2008/6/30 Nick Holland <[EMAIL PROTECTED]>: > > Eduardo Alvarenga wrote: > > Hi guys, > > > > I'm willing to port all DJB's public domain software, including djbdns, > > qmail, daemontools, etc. > > If made, It can be easily accepted on ports or, for historical reasons, i > > will not be imported?
<snip> > > Here are some of the issues that I know you will run into: > > Do you "normalize" his directory layout, or do you maintain his > suggested layout (which has its merits, but is VERY non-hier(7)). > > IF you normalize his layouts, you annoy the current DJBDNS > users and confuse the new ones. How do you propose to > announce this to the port user and orient them appropriately? > > IF you don't normalize his directory layouts...I doubt they > will be imported when you slop three new directories in /. I think about respecting hier(7) and follow /usr/local, then warn the user about creating symlinks to the "original" folders if he wishes. I personally use /etc/djbdns as the main folder, others don't. > Do you maintain the DJBDNS "dependency" on daemontools, even > though djbdns is one (er..two!) app(s) that just doesn't need > to be restarted when it fails (because it doesn't)? daemontools will only be listed as a RUN dependency. The configuration will be up to the user that can choose to run it the way he wants, by using daemontools or not. > IF you separate them, again, you will need to develop docs. The port is supposed to only install the software, and not to configure it. The SA needs to read the official documentation for that. > IF you leave them together...what value do you add to the > port? <snip> > I think similar arguments can be made against a qmail port. Sure, I'll also respect hier and then allow the SA to create the necessary symlinks, or even create a script to make it more automatic. > Some of his utility programs (ucspi-tcp) would be really > handy ported, and I can not think of any issues involved > there. So there's a partial yes. :) Regards, -- Eduardo Alvarenga
