Add images to `trunk/Identity/Images/Webenv' directory:
    
        - Image files shouldn't be versioned. They are produced when the
          `prepare' functionality of `centos-art.sh' script is executed
          and, this way, made available for all components inside the
          working copy to make use of them. Nevertheless, it is not
          possible for CGI scripts to directly reach images from the
          working copy, at least we make them public through the web
          server the CGI script is runnig on.
          
        - At this point the following options come to my mind and a
          compromise between them must be taken, considering possible
          security and maintainance issues of all involved components:
    
          1. Adding PNG images, produced in the working copy, up to the
          repository so they can be accessed through an URL. 
          
                This would make the image files available through a web
                server (the subversion web server in this case), but it
                would be needed for the web application to realize
                external requests in order to load images (in case both
                the subversion server where the repository is stored in
                and the web server where the CGI application is running on
                be different one another). Also, in this configuration,
                images could change unexpectedly inside the subversion
                server and that is not a good thing for the web
                application. So, I like to thing about images as if they
                were part of the web application source code itself.
    
          2. Adding PNG images, produced in the working copy, up to the
          repository in order to `checkout' them later from the repository
          down to the location where the `centos-web.cgi' is maintained in
          the working copy. 
          
                Notice that CGI scripts like `centos-web.cgi' are
                versioned inside the repository but made available in a
                place different to that one refered on the repository. For
                example, in the central repository, the `centos-web.cgi'
                script is stored in the location
                `/trunk/Scripts/CentOS-Web', but in the working copy it is
                not placed at
                `/home/centos/artwork/trunk/Scripts/CentOS-Web' as you
                might expect. Instead, it is stored at
                `/home/centos/public_html/CentOS-Web/' using the same
                `checkout' technic I pretend to use with images stored at
                `/trunk/Identity/Images/Webenv' which would be place at
                `/home/centos/public_html/CentOS-Web/Public/Images'
                directory.  This last directory is prepared (through an
                apache configuration file) to permit execution of CGI
                script so we can simulate a real server environment
                without lossing the posibility of keeping ourselves
                working on a version controlled environment.