This part of the documentation is not meant for end users of Coppermine, but only for developers. There is no support for this section, it comes as-is.
This document is meant to explain what needs to be done by developers when adding / renaming / deleting files to/from the SVN during development stage.
Refer to the section "Naming Conventions" when adding new files or renaming existing files.
If a developer needs to add a new file to Coppermine's core, here's a list of things that needs to be done:
/************************* Coppermine Photo Gallery ************************ Copyright (c) 2003-2011 Coppermine Dev Team v1.0 originally written by Gregory Demar This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License version 3 as published by the Free Software Foundation. ******************************************** Coppermine version: 1.5.12 $HeadURL$ $Revision$ **********************************************/For other file types (e.g. sql files), different comment symbols might apply.
If a file name can not be kept (e.g. because of collision with naming conventions), it should be renamed instead of deleting the old one and creating a new one. The benfit of renaming is the fact that the version history will be kept in the Subversion repository.
Once a file has been renamed in SVN, you will have to make additional edits:
In a nutshell: what has been said above about renaming files applies to deleting files as well: after having deleted the file in SVN, make sure to edit the XML file used for versioncheck and the array of files scheduled for deleting by the updater.
Keep in mind though that before deleting core PHP files, you should discuss this with your fellow devs first on the dev-only board.