On Wed, Mar 11, 2015 at 07:03:14PM -0700, Benjamin Perrault wrote: > Hi all, >
Hi, > So a while back - I mailed the list ( > http://article.gmane.org/gmane.mail.opensmtpd.general/2397 ) about OpenSMTPD > - but since I didn???t hear anything back, I went thru, sorted the issues ( > both build and runtime ) and have it working on OS X Yosemite. > > I???m not sure if this is of any use to anyone but me, but I???m hoping it > is. If anything, it???s a first step getting OpenSMTPD into Homebrew or > Macports, amongst other things. > > So.. > Well, to be perfectly clear about our position: We are not necessarily interested _ourselves_ in porting to all systems, primarily because unless there's high demand it diverts our efforts from working on features that more people expect. However, we greatly appreciate when people do the porting and we do want to help them merge their changes so that OpenSMTPD runs on as many hosts as possible. If OpenSMTPD doesn't run on a system and you don't see us working on it, or you see that a ticket for portability stalls, it doesn't mean we dont care but just that we'd appreciate if someone else did the work ;-) > ---------- > b.) Patches > > What???s the best way to handle these? > > I have a quick and dirty patch ( like you would see in Homebrew or even > FreeBSD ports ) that will allow everything to build/work correctly after > it???s applied to the 5.4.4p1 source tree. Since some of the OS X changes do > break the build on the other BSDs, this might be a good idea ( this is even > more an prevalent in the latest portable snapshot ). It???s not something you > would put in a git pull request, that???s for sure. But it works. > > Or I can spend some time and make a not-so-dirty patch that can be applied > without breaking non-OS X builds.. but I???m not sure the code/style > guidelines, nor am I 100% sure how to cleanly apply the needed changes - so I > might need a little help and this will. It would be an undertaking. > > Or I can do both. Or some hybrid.. Or.. basically, I don???t really know what > the best way to handle it. What says the development team / community say? > First of all, you need to separate the changes you did to allow the project to build, from the packaging you did so it can install on your system. Our portable branch only focuses on making the project build on systems disregarding how it will be packaged. Any diff you have to make it build we can review and either merge or help you modify so that it can be made into a diff suitable for merge. I'd say, the first step would be to share the diffs :-) > Anyway - thanks to the OpenSTMPD team for building such a great SMTP server - > I hope this work will be useful to someone and contributes to OpenSMTPD???s > total domination. > Total domination is in progress. -- Gilles Chehade https://www.poolp.org @poolpOrg -- You received this mail because you are subscribed to [email protected] To unsubscribe, send a mail to: [email protected]
