wip/edoc initial package 0.1.0 - please review

Brendon Costa <[email protected]>
Newsgroups gmane.os.netbsd.devel.pkgsrc.wip.review
Message-ID <[email protected]>
Hi all,

I have completed creating a package for EDoc++ that is pending review of
other NetBSD users. This is my first attempt at creating a pkgsrc
package, so there may be some issues that i am un-aware of. It builds
and installs fine on a fresh install of i386 NetBSD 3.0 for me.


EDoc++ is a tool for C/C++ developers that automates many exception
safety analysis checks and provides detailed documentation about
exception propagation through the code.


The website for edoc is located at:
http://edoc.sourceforge.net/index.html


For information on EDoc++ usage please see the Basic Usage chapter (6)
of the user manual at:
http://edoc.sourceforge.net/EDocManual/index.html


EDoc++ includes a set of tests that you can run (Which are not
installed) from the packages work directory. To execute the tests after
building and installing it:

cd /usr/pkgsrc/wip/edoc/work/edoc-0.1.0/
./run_tests.sh

I did not provide a patch for this shell script that runs the unit
tests. Basically the shell script requires a python >= 2.4 interpreter
which it invokes with the tests which are written in python. However the
shell script that spawns it just runs the binary: "python" which does
not exist in pkgsrc. Either setup a symlink for python -> python2.4 or
as i do to run the tests you can simply edit the shell script and change
the call from: "python" to "python2.4". I felt that it was not worth
creating a patch for this as it will never be seen by the end users.

Thanks,
Brendon.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.