Determine why the gCal file instead of gCal folder is created.

##Problem##

In order to clone the gCal sync process to folder /home/<linux username>/maintenance/gCal/, the gCal folder must be created, howerver, a file called gCal is created with the content of the customLocalServer.py.

##Prediction##

Probably because changing a hardCoded name to a variable name returned a null value instead of a correct value, which reduced the target path to end in gCal instead of gCal/customLocalServer.py. That would mean the copy of customLocalServer.py would be renamed to a file named gCal.

##Prediction analysis##

However, a thought and a combination of thought and observation contradict this prediction:

1. I think the customLocalServer.py was not hardCoded in the first place, and I think that has been the only change since this problem has arisen.


2. I think the customLocalServer.py is only exported/copied once (unless it is moved afterwards from maintenance to maintenance/gCal/taskw_gcal_sync to allow an empty gCal folder for cloning the repo), that would mean that the exporting of customLocalServer.py failed but it has not failed, the file is exported correctly.