Creating and maintaining skins

Here's how the skins were originally built for the launch of Conifer. Dan wrote the copy_opac() function in ​http://svn.open-ils.org/trac/ILS-Contrib/browser/conifer/trunk/tools/patch_conifer.sh to do the following:

1. For the default skin, create an /openils/var/web/opac/skin/ subdirectory named default_test
2. Copy the customized default files that we want to be common to all Conifer skins over top of the files in /openils/var/web/opac/skin/default_test
3. For each skin, create an /openils/var/web/opac/skin/ subdirectory named "$skin"_test, then:
   1. Copy the contents of the default skin (/openils/var/web/opac/skin/default/*) into "$skin"_test
   2. Copy the default_test skin into place as "$skin"_test
   3. Copy the custom skin files over top "$skin"_test
   4. Munge the links to point to default_test for rdetail.js
   5. Munge the links to point to "$skin"_test for all

The design goal was to keep the smallest set of changes in Subversion as possible, and to put as much intelligence into the patch_conifer.sh script as possible, so that upgrades would not be too disruptive.

With the latest upgrade to comet, I believe that Robin added a step that keeps opac/skin/default pristine and created opac/skin/default_conifer containing all of the customizations common across Conifer that the other skins should inherit from.