Hi, I've seen that my DJB packages are already in CVS. That's great. And the compiled packages are also already available in the repository. This may not be so great. Haven't thought of that. DJB software has a very strange licensing. He allows distribution of binary packages only when installing the binary package does EXACTLY the same thing as when installing the packages manually by using the original source code. This is quite difficult. Especially because the original source is not compilable anyway because of the common errno problems with all somewhat modern linux dists... ;-)
Debian does not provide binary DJB packages because of these license restrictions. They just provide installer packages. I see three solutions: 1. Ignore the problem... Not the most legal solution... 2. Make sure the packages install EXACTLY as DJB wants it. This means installing the binaries in /command instead of /usr/bin. And this also means that we can't apply any patches to the source. If the errno patch, which is needed for successful compiling, is already violating the license is unclear but personally I think this is ok because it doesn't change the behavior of the programs. I don't like this solution at all and I'm pretty sure Thorsten (Who said he uses a heavily patched djbdns) don't like it either. But if it's decided that this solution is the best one then I could modify the Makefiles so the packages are compatible to DJB standards. 3. Exclude these packages from automatic inclusion in the binary repository on freewrt.org. This type of software can then only be installed by creating the packages with the build system or by compiling the packages directly into the freewrt image. This treatment is then comparable to the Debian-way and as a Debian developer I'm used to it and I prefer and recommend this solution. If this all sounds to "non-free" for "free"wrt then maybe a forth solution is removing the packages completely again. I could understand that. I like DJB software a lot but unfortunately the licensing is very unfriendly to distributors. As I said, I would suggest solution 3. Maybe it could be implemented by adding an option to the control file which defines that the package is source-only and the automatic building of packages for the binary repository then ignores such packages. Or maybe simpler: Just implement a package-blacklist in the script which automatically build the packages for the binary repository. -- Bye, K <http://www.ailis.de/~k/> [A735 47EC D87B 1F15 C1E9 53D3 AA03 6173 A723 E391] (Finger [EMAIL PROTECTED] to get public key) _______________________________________________ freewrt-developers mailing list [email protected] https://www.freewrt.org/lists/listinfo/freewrt-developers
