Opened 9 years ago
Last modified 9 years ago
#48917 new submission
new port: naviserver
Reported by: | gustafn | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.3 |
Keywords: | Cc: | ||
Port: |
Description
NaviServer is a C implemented WebServer with multi-protocol support, maintained at bitbucket (https://bitbucket.org/naviserver/naviserver). The NaviServer repository (https://bitbucket.org/naviserver/) contains about 50 modules, most of these are implemented in C. These modules are compiled into .so files.
The typical structure of an naviserver installation contains the following directories:
/usr/local/ns/ /usr/local/ns/bin/ /usr/local/ns/conf/ /usr/local/ns/include/ /usr/local/ns/lib/ /usr/local/ns/modules/ /usr/local/ns/pages/ /usr/local/ns/tcl/ /usr/local/ns/vhost/
where ns/bin contains the naviserver binaries (most prominently: nsd) and the .so files of the modules (e.g nscgi.so, ..., nsdbpg.so), and ns/lib contains extra packages (.tcl and .dylib). The 50 ~extra modules contain e.g nsdbpg (postgres interface), nsssl (SSL/TLS), nsudp, or nssmtp. The .so files of these modules are just useful for NaviServer.
Therefore, the attached portfile uses essentially the same structure as above, using /opt/local/var/log/ns/ as log directory. This structure is similar to the apache2 tree but violates the mtree. The advantage of using the structure is that the standard config files and install scripts of the packages work mostly out of the box.
With separate tickets i will submit naviserver-nsdbpg and naviserver-libthread. At some later time i will be working on a portfile for OpenACS, that will require amonst other things naviserver-nsdbpg and naviserver-libthread.
Added missing backslash in description