mkmed automatically generates package build scripts and related files. Unlike make, mkmed works bottom-up, so it can infer information you would otherwise have to specify explicitly.
This package is discussed on the mkmed list. New releases are announced on the prjware-announce list.
mkmed is devoid of warranty and is distributed under the GNU General Public License, version 2. But that doesn't mean it's necessarily a good idea for you to distribute modified versions. (That includes repackaging.) I'd like to know if you plan to do that.
Older versions are published for historical interest.
slashpackage is a good thing. You can
read more about it
here. If you don't already have
/package, create it (on any
filesystem you like, as long as it's accessible by the name
# mkdir -p /usr/local/package # ln -s /usr/local/package / # chmod +t /package/.
# sp-install mkmed-VERSION.tar.bz2
Or, if you like to do things manually, unpack the tarball and run
# cd /package # bunzip2 < /path/to/mkmed-VERSION.tar.bz2 | > tar -xpf - # cd prog/mkmed-VERSION # package/install
more detailed instructions.
Very incomplete. Thomas Schwinge has some supplemental documentation.
#includedirectives may fail, or may include the wrong file. Workaround: arrange your files so that no file includes another file from a different directory.