Standardizing Configuration Tasks
The prepare functionality is the
interface the centos-art.sh script provides
to standardize the final configuration stuff your workstation
needs, once the working copy of &TCAR; has been downloaded
inside it already.
Assuming this is the very first time you run the
centos-art.sh script, you'll find that
it isn't found in your workstation. This is correct because
you haven't created the symbolic link that make it available
in the execution path, yet. In order to make the
centos-art.sh script available in the
execution path of your workstation, you need to run it using
its absolute path first:
~/Projects/artwork/trunk/Scripts/centos-art.sh prepare [OPTIONS]
Later, once the centos-art.sh script is
available in the execution path of your system, there is no
need for you to use the absolute path again. From this time
on, you can use the centos-art command-line
interface directly, as the following example describes:
centos-art prepare [OPTIONS]
The prepare functionality accepts the
following options:
Supress all output messages except error messages. When this
option is passed, all confirmation requests are supressed and
a possitive answer is assumed for them, just as if the
option whould have been provided.
Assume yes to all confirmation requests.
This option verifies packeges required by
centos-art.sh script. installs or updates
required packages. When required packages aren't installed,
this option uses sudo yum install
command to perform the installation task. When required
packages are installed, this option uses sudo yum
update to update them, if there is any related
actualization to be applied on. In both cases, it is required
that you configure the sudo command first,
as described in .
This option maintains the file relation between your working
copy and configuration files inside your workstation through
symbolic links. When you provide this option, the
centos-art.sh puts itself into your
system's execution path through its command line interface
centos-art and makes common brushes,
patterns, palettes and fonts inside the working copy,
available to applications like GIMP in order for you to make
use of them without loosing version control over them.
This option removes all common fonts, brushes, patterns, and
palettes currently installed in your home directory, in order
to create a fresh installation of them all again, using the
working copy as reference.
This option initializes image files inside the working copy.
When you provide this option, the
centos-art.sh scripts renders image files
from all design models available in the working copy. This
step is required in order to satisfy file dependencies among
different components inside the working copy.
This option initializes documentation files inside the working
copy. When you provide this option, the
centos-art.sh script renders all
documentation manuals from their related source files to
different output formats, so you can read them nicely.
Print the name and value of some of the environment variables
used by centos-art.sh scripts as described
in .
When no option is provided to prepare
functionality, the centos-art.sh script
uses the ,
, and
options as default behaviour.
Otherwise, if you provide any option, the
centos-art.sh script avoids its default
behaviour and executes the prepare
functionality as specified by the options you provides.
Notice that it is possible for you to execute the
prepare functionality as much times as
you need to. This is specially useful when you need to keep
syncronized the relation between content produced inside your
working copy and the applications you use outside it. For
example, considering you've added new brushes to or removed
old brushes from your working copy of &TCAR;, the link
information related to those files need to be updated in the
~/.gimp-2.2/brushes
directory too, in a way the addition/deletion change that took
place in your working copy can be reflected there, as well.
The same is true for other similar components like fonts,
patterns and palettes.