> > Unlike other internet packages, there is no configure script. > > (Big hint to Neale. Even just a dummy.) > > Why?
Because I would like to treat CPINT the same as the bazillion other packages I use when I [re]build Linux. A dummy configure script is harmless and leaves the door open for changes if (when!) it needs a config step. If CPINT is truly self-configuring and never will need a separate step for config, then fine. There is a work-around where I use 'true' instead of './configure', but were the day to come that CPINT really needed a config script it would be a hassle and silly to have to change. > If people start editing the makefile too much (that is: you start > editing the makefile to much on startdard usage and/or get enough mail > asking about this) then you should consider an autoconf script. I guess that's what I'm saying. > Other than that: a clear README/INSTALL is enough. Not that it isn't clear. Just that it may be more complicated w/r/t build automation. -- RMT --A5E937985.1054481495/rmt-desk.bmc.com--
