Forum OpenACS Development: Making OpenACS4 believe in itself
Since we're close to an (alpha) release, this sort of stuff becomes worth doing IMO, so that we don't cause aD unwanted grief when newbie installers go to them for help with OpenACS 4.x!
BTW bafs #1120 and 1121 now exist and point at these patches:
There are a lot of references to aD in the documentation, but acs-core-docs is not yet 'PORTED' so presumably those "don't count" at this stage?
I also applied your autoinstaller patch ...
diff -uNrfrom above the place where you untar the tarball (and later applying with -p1) is a common RPM world convention, so it is what I tend to do out of habit. I'll try using
cvs -z3 -q diff -N -ufor OpenACS4 from now on.
BTW, you've apparently not committed those patches yet... I just did a cvs update, and they didn't show up here. No rush at all, I'm glad they were useful.
I've been waiting for Roberto's "doc doc" to go public, for a while now... I'll send him email and see if I can be useful.
The SDM probably needs to let the admin choose what directory to CD to
when running patch, and what -pN value to run patch with.
It would also be slick if it would let you optionally upload your new version of a file and generate the patch for you against the current cvs source, then let you
inspect and confirm it.