

Submitted by:   pguyot@

Paul's proposed (untested?) additions to provide the script with a proper
environment in order to perform successful "cvs ci" 's on the freshly generated
Index, so that it exists both in CVS and rsync all the time.

NOTE: I currently don't have the time to pursue this further until completion
and I don't want anyone to think I'm holding it back. So if anyone feels up to the
challenge then please be my guest! I admit I have no idea how the scenario will finally
look like if these additions are adopted, what the script's requirements will be, what box
it will run on, under what permissions and what dp installation it will need/use.
So please test thouroughly before pushing live and replacing what currently works,
though admittedly in a limited fashion.

PS: Once the Index is again constantly refreshed in CVS through this script, developers
should still keep from committing one themselves, as this could cause potential clashes
with an Index that is known to be accurate (based on a 100% guaranteed "clean" dports/ tree).

git-svn-id: 620571fa9b4bd0cbce9a0cf901e91ef896adbf27@14470 d073be05-634f-4543-b044-5fe20cf6d1d6

macports/macports-base,neverpanic/macports-base,danchr/macports-base,neverpanic/macports-base,macports/macports-base,danchr/macports-base