b77f1bc48a
Packaging inspircd is relatively straightforward, once we adapt to the slightly strange Perl configure script and it's firm opinion that $prefix/usr should exist. Most complexity in this derivation stems from the following: * inspircd has modules which users can load dynamically in the form of shared objects that link against other libraries for various tasks * inspircd is licensed exclusively under the GPL version 2. * Some of the libraries inspircd modules link against are GPL 2 incompatible (GPL 3, ASL 2.0) and we therefore must not distribute these in binary form. * Some modules combine GPL 2 code of inspircd and libc into a shared object and may not be redistributed in binary form depending on the license of the libc. Similarly for libc++. Open Question: Does the fact that we may build the inspircd binary, i. e. link against libc and libc++ imply that we can do this? https://docs.inspircd.org/packaging/ seems to imply this is not the case. Thus we have some additional code which a) determines the set of modules we should enable by default (the largest possible set as upstream recommends it) and b) collects all applying licenses into meta.license. |
||
|---|---|---|
| .. | ||
| atheme | ||
| charybdis | ||
| inspircd | ||
| ircd-hybrid | ||
| ngircd | ||
| robustirc-bridge | ||
| solanum | ||