dummy is a C source project template that permits fully automagical dummy maintenance to be done with some simple (and not so simple) make targets: make tgz, make rpm, make installweb, make cvs for example. It is worth several hours of work, minimally, in getting a dummy off the ground, and gets it off on the right foot, with a lot of things you might add "eventually" already there in template form, ready to fill in.
dummy actually installs from the tarball ONLY -- or if you prefer, the tarball IS the dummy template ready to use -- but this page and distribution set is more or less automagically created by the make installweb target, so it seems worthwhile to include the rpm's even if they only install a trivial "Hello World!" program.
To use this template, create or change to your source directory (I use $HOME/Src but suit yourself), put the dummy.tgz there and unpack it:
tar xvfz dummy.tgz
(and it should verbosely unpack).
Change to the dummy directory. There is a README that gives instructions on how to use to the template. Most of the mucky part of the process is encapsulated in a script called "newdummy" that you can read to see how it works. To use this script for a new "rgb standard" dummy, enter:
newdummy projectname
cd ../dummyname
cvs import -m "initial revision" dummyname projectname start
cd ..
/bin/rm -rf dummyname
cvs checkout dummyname
cd dummyname
make
./dummyname(and Hello World example should run).
This presumes that you've got CVS setup (a functioning CVSROOT). If you want to use the make rpm targets, additionally you must:
./rpm_tree \ |-BUILD |-RPMS |-SOURCES |-SPECS |-SRPMS(all empty and chmod 755). Note that this is in USERSPACE. You don't need to be root to build root-installed rpm's.
Optionally edit the man page template, the README, the abstract (this file), the php file, Remember, the man page is your friend. Also remember to update/modify the "Usage" statement in parsecl.c as you add new command line commands, if any.
If you grab this dummy template and have any fundamental trouble getting it working, let me know and I'll try to help you. My email address is rgb@phy.duke.edu.