Why so many Concrete Source versions on site

Permalink
I've recently upgraded to C5.5.2 and everything's fine with the site. I've discovered in doing an FTP download backup of the site that there are two versions of Concrete5 source under "files/tmp/concrete5.5.1" and "files/tmp/concrete5.5.2" and two other versions under "updates/concrete5.5.1" and "updates/concrete5.5.2".

Besides the regular "concrete" area, why these other copies?
And how do they get cleaned up? I can only assume by hand !
Most of the FTP download time is consumes by these areas.
Thanks,
Dennis

tdpss
 
tdpss replied on at Permalink Reply
tdpss
I mispoke, the versions concrete5.5.2 listed in original posting is really version 5.4.2.2.
tdpss replied on at Permalink Reply
tdpss
More on Update, I'm actually on the latest version 5.5.1. As it turns out, the update directory is needed as part of the core concrete area. I assume that's because I performed an update to the latest version.

So, don't anyone think these are deletable files.

Don't know about the files/tmp/ area yet. Glad Concret5 version deploys aren't too numerous. I can see this file structure method getting out of hand over time, let alone burdening backups with more and more core files.
WebcentricLtd replied on at Permalink Reply
if you want to clear up the update directories at some point in the future you can do.

You just need to make sure that the override in the config/site.php file is removed...

for example - define('DIRNAME_APP_UPDATED', 'concrete5.4.2.1');?>

and of course if you do that make sure you copy the contents of /updates/concrete5.4.2.1 (in this particular case) are copied into your root/concrete directory