On 4/3/06, Charlie Brady wrote: > > It's there in the djbdns install doco, but hasn't yet been added to the > daemontools (or ucspi-tcp, qmail, publicfile etc) install instructions: > > http://cr.yp.to/djbdns/install.html > > So if you are ultra cautious, you may feel there is no approved > workaround. But I think that DJB's intentions are clear enough. Ask a > lawyer if you want a better opinion.
DJB's distributors.html page makes it clear that one can distribute binaries that are identical to ones a user would create. Editing error.h results in indentical binaries compared to including errno.h in conf-cc. You seem be saying distributors.html is invalid based on some unreferenced DJB licensing requirement. I think it's pretty clear what DJB's intentions are but my understanding is different than yours because you are using some unreferenced requirement that is incompatible with DJB's published requirements. I'm starting to understand why some people have problems with DJB's licensing. Thankfully I won't be using tcpserver or daemontools. I believe it's "-include". "-include" and "--include" both work. The djbdns instructions are: > > 4. Compile the djbdns programs: > > echo gcc -O2 -include /usr/include/errno.h > conf-cc > make Feel free to add to, modify, or remove from the wiki since you seem to really care about DJB's exact syntax and unreferenced / incompatible licensing requirements. In any event, the current instructions work and I've decided stay away, far away, from DJB code after all of this. Per another thread, I'm hoping there will be more support for init.d/rc script distribution so these DJB licensing issues can be avoided altogether. It's quite mind boggling. John
