|
 |
d7b2cd |
% Part : Preparing Your Workstation
|
|
|
d7b2cd |
% Chapter: Configuration
|
|
|
d7b2cd |
% ------------------------------------------------------------
|
|
|
d7b2cd |
% $Id: configuration.tex 6191 2010-08-02 02:36:14Z al $
|
|
|
d7b2cd |
% ------------------------------------------------------------
|
|
|
d7b2cd |
|
|
|
d7b2cd |
This chapter describes configurations you need to set up before using
|
|
|
d7b2cd |
CentOS Artwork Repository.
|
|
|
d7b2cd |
|
|
|
d7b2cd |
\section{Firewall}
|
|
|
d7b2cd |
|
|
|
d7b2cd |
The CentOS Artwork Repository lives on the following URL:
|
|
|
d7b2cd |
|
|
|
d7b2cd |
\begin{quote}
|
|
|
d7b2cd |
https://projects.centos.org/svn/artwork/
|
|
|
d7b2cd |
\end{quote}
|
|
|
d7b2cd |
|
|
|
d7b2cd |
To reach this location you need to have Internet access and be sure no
|
|
|
d7b2cd |
rule in your firewall is denying this site. Note that the URL uses the
|
|
|
d7b2cd |
SSL protocol (port 443).
|
|
|
d7b2cd |
|
|
|
d7b2cd |
\section{Subversion Behind Squid}
|
|
|
d7b2cd |
|
|
|
d7b2cd |
Sometimes it is convenient to proxy Subversion client's requests
|
|
|
d7b2cd |
through a proxy-cache server like Squid. In cases like this, the Squid
|
|
|
d7b2cd |
proxy server is in the middle between you and CentOS Artwork
|
|
|
d7b2cd |
Repository. If you want to proxy Subversion client's requests through
|
|
|
d7b2cd |
Squid proxy-cache server, you need to configure your Subversion client
|
|
|
d7b2cd |
and your Squid proxy server to do so.
|
|
|
d7b2cd |
|
|
|
d7b2cd |
\subsection{Subversion Client Configuration}
|
|
|
d7b2cd |
|
|
|
d7b2cd |
Subversion client needs to be configured to send requests to your
|
|
|
d7b2cd |
Squid proxy-cache server. This configuration takes place in the file
|
|
|
d7b2cd |
\texttt{$\sim$/.subversion/servers}.
|
|
|
d7b2cd |
|
|
|
d7b2cd |
\subsection{Squid Server Configuration}
|
|
|
d7b2cd |
|
|
|
d7b2cd |
Squid proxy-cache server needs to be configured to accept the
|
|
|
d7b2cd |
extension methods \texttt{REPORT MERGE MKACTIVITY CHECKOUT MKCOL}.
|
|
|
d7b2cd |
This configuration takes place in the file
|
|
|
d7b2cd |
\texttt{/etc/squid/squid.conf}, specifically in the configuration tag
|
|
|
d7b2cd |
illustrated in \autoref{fig:Workstation:Configuration:Squid}.
|
|
|
d7b2cd |
|
|
|
d7b2cd |
\begin{figure}[!hbp]
|
|
|
d7b2cd |
\hrulefill
|
|
|
d7b2cd |
\begin{verbatim}
|
|
|
d7b2cd |
# TAG: extension_methods
|
|
|
d7b2cd |
# Squid only knows about standardized HTTP request methods.
|
|
|
d7b2cd |
# You can add up to 20 additional "extension" methods here.
|
|
|
d7b2cd |
#
|
|
|
d7b2cd |
#Default:
|
|
|
d7b2cd |
# none
|
|
|
d7b2cd |
extension_methods REPORT MERGE MKACTIVITY CHECKOUT MKCOL
|
|
|
d7b2cd |
\end{verbatim}
|
|
|
d7b2cd |
\hrulefill
|
|
|
d7b2cd |
\caption{Squid configuration to proxy Subversion client's requests.%
|
|
|
d7b2cd |
\label{fig:Workstation:Configuration:Squid}}
|
|
|
d7b2cd |
\end{figure}
|
|
|
d7b2cd |
|
|
|
d7b2cd |
\section{Working Copy}
|
|
|
d7b2cd |
|
|
|
d7b2cd |
A Subversion working copy is an ordinary directory tree on your local
|
|
|
d7b2cd |
system, containing a collection of files (i.e. Translations, Designs,
|
|
|
d7b2cd |
Manuals, and Scripts). You can edit these files however you wish. Your
|
|
|
d7b2cd |
working copy is your own private work area: Subversion will never
|
|
|
d7b2cd |
incorporate other people's changes, nor make your own changes
|
|
|
d7b2cd |
available to others, until you explicitly tell it to do so. You can
|
|
|
d7b2cd |
even have multiple working copies of the same project.\footnote{Even
|
|
|
d7b2cd |
this is basically correct, doing so when using CentOS Artowrk
|
|
|
d7b2cd |
Repository can bring some confusion when executing scripts. Presently,
|
|
|
d7b2cd |
only one absolute path can be defined as absolute path for scripts'
|
|
|
d7b2cd |
execution. You can have as many working copies of CentOS Artwork
|
|
|
d7b2cd |
Repository as you want but scripts will be executed from just one
|
|
|
d7b2cd |
working copy absolute path. That is, the one stored under
|
|
|
d7b2cd |
\texttt{/home/centos/artwork/}}.
|
|
|
d7b2cd |
|
|
|
d7b2cd |
Once you've made some changes to your working copy files and verified
|
|
|
d7b2cd |
that they work properly, Subversion provides you with commands to
|
|
|
d7b2cd |
``publish'' your changes to the other people working with you on your
|
|
|
d7b2cd |
project (by writing to the repository). If other people publish their
|
|
|
d7b2cd |
own changes, Subversion provides you with commands to merge those
|
|
|
d7b2cd |
changes into your working directory (by reading from the repository).
|
|
|
d7b2cd |
|
|
|
d7b2cd |
\begin{figure}[!hbp]
|
|
|
d7b2cd |
\hrulefill
|
|
|
d7b2cd |
\begin{verbatim}
|
|
|
d7b2cd |
svn co https://projects.centos.org/svn/artwork /home/centos/
|
|
|
d7b2cd |
\end{verbatim}
|
|
|
d7b2cd |
\hrulefill
|
|
|
d7b2cd |
\caption{Subversion command used to download the working copy.%
|
|
|
d7b2cd |
\label{fig:Workstation:WC:Download}}
|
|
|
d7b2cd |
\end{figure}
|
|
|
d7b2cd |
|
|
|
d7b2cd |
The subversion command illustrated in
|
|
|
d7b2cd |
\autoref{fig:Workstation:WC:Download} brings a CentOS Artwork
|
|
|
d7b2cd |
Repository working copy down to your workstation, specifically to your
|
|
|
d7b2cd |
home directory (\texttt{/home/centos/artwork/}). This process may take
|
|
|
d7b2cd |
some time. Once the working copy is available in your workstation,
|
|
|
d7b2cd |
you are ready to start exploring and improving available works.
|
|
|
d7b2cd |
|
|
|
d7b2cd |
Note that you need to have a username called \texttt{centos} in your
|
|
|
d7b2cd |
system. If you don't have it, you can create it using the comand
|
|
|
d7b2cd |
\texttt{useradd} as superuser (\texttt{root}).
|
|
|
d7b2cd |
|
|
|
d7b2cd |
\subsection{Standardizing Absolute Path}
|
|
|
d7b2cd |
|
|
|
d7b2cd |
When using Inkscape to import raster images inside SVG files the
|
|
|
d7b2cd |
absolute image path is required. If everyone stores the working copy
|
|
|
d7b2cd |
on a different absolute path imported images will not be loaded in
|
|
|
d7b2cd |
those location different from those they were conceived. There is no
|
|
|
d7b2cd |
way to find the right absolute image path but defining a convenction
|
|
|
d7b2cd |
about it.
|
|
|
d7b2cd |
|
|
|
d7b2cd |
On a path string (e.g., /home/centos/artwork/trunk/) the username
|
|
|
d7b2cd |
(`centos') is the variable component, so it is the component we need
|
|
|
d7b2cd |
to standardize--in the sake of keeping the working copy inside user's
|
|
|
d7b2cd |
/home/ structure. Thus, analysing which username to use, the CentOS
|
|
|
d7b2cd |
Project is what join us all together, so the `centos' word in
|
|
|
d7b2cd |
lower-case seems to be a nice choise for us to use as common username.
|
|
|
d7b2cd |
|
|
|
d7b2cd |
\section{User Identification}
|
|
|
d7b2cd |
|
|
|
d7b2cd |
At this point you probably have made some changes inside your working
|
|
|
d7b2cd |
copy and wish to publish them. To publish your changes on CentOS
|
|
|
d7b2cd |
Artwork Repository you need to have a registered account with commit
|
|
|
d7b2cd |
privilege in CentOS Artwork Repository.
|
|
|
d7b2cd |
|
|
|
d7b2cd |
If you are new in CentOS Artwork Repository it is possible that you
|
|
|
d7b2cd |
can't commit your changes. That is because new registered accounts
|
|
|
d7b2cd |
haven't commit privilege set by default. In order for your registered
|
|
|
d7b2cd |
account to have commit privilege inside CentOS Artwork Repository you
|
|
|
d7b2cd |
need to request it. See section
|
|
|
d7b2cd |
\ref{sec:Configuration:User:Privileges}.
|
|
|
d7b2cd |
|
|
|
d7b2cd |
\subsection{User Account Registration}
|
|
|
d7b2cd |
\label{sec:Configuration:Account}
|
|
|
d7b2cd |
|
|
|
d7b2cd |
To register a user account inside CentOS Artwork Repository, you need
|
|
|
d7b2cd |
to go to the following URL:
|
|
|
d7b2cd |
|
|
|
d7b2cd |
\begin{quote}
|
|
|
d7b2cd |
\url{https://projects.centos.org/trac/artwork/}
|
|
|
d7b2cd |
\end{quote}
|
|
|
d7b2cd |
|
|
|
d7b2cd |
\subsection{User Account Privileges}
|
|
|
d7b2cd |
\label{sec:Configuration:User:Privileges}
|
|
|
d7b2cd |
|
|
|
d7b2cd |
To have commit privileges in CentOS Artwork Repository it is needed
|
|
|
d7b2cd |
that you show your interest first, preferably with something useful
|
|
|
d7b2cd |
like a new or improved design, translation, manual, or script. As
|
|
|
d7b2cd |
convenction, people working on CentOS Artwork Repository share ideas
|
|
|
d7b2cd |
in the mailing list
|
|
|
d7b2cd |
\href{mailto:centos-devel@centos.org}{centos-devel@centos.org}. If you
|
|
|
d7b2cd |
are interested in joining us go there and express yourself.
|
|
|
d7b2cd |
|
|
|
d7b2cd |
\section{Repository Tagged Revisions}
|
|
|
d7b2cd |
|
|
|
d7b2cd |
The CentOS Artwork Repository is also available as tagged revisions.
|
|
|
d7b2cd |
Tagged revisions are checkpoints on the CentOS Artwork Repository
|
|
|
d7b2cd |
developing lifetime. They are inmutable copies of the CentOS Artwork
|
|
|
d7b2cd |
Repository state through time. Tagged revisions contain the files
|
|
|
d7b2cd |
used to produce images but not images themselves. Inside tagged
|
|
|
d7b2cd |
revisions you can find scripts (\texttt{.sh}), design templates
|
|
|
d7b2cd |
(\texttt{.svg}), translation files (\texttt{\.sed}), gimp projects
|
|
|
d7b2cd |
(\texttt{.xcf}), and documetation files (\texttt{.tex}).
|
|
|
d7b2cd |
|
|
|
d7b2cd |
CentOS Artowrk Repository tagged revisions are available for
|
|
|
d7b2cd |
downloading in the following location:
|
|
|
d7b2cd |
|
|
|
d7b2cd |
\begin{description}
|
|
|
d7b2cd |
\item[URL:] https://projects.centos.org/svn/artwork/tags
|
|
|
d7b2cd |
\end{description}
|
|
|
d7b2cd |
|
|
|
d7b2cd |
and alternatively, you can find references in the CentOS Project's
|
|
|
d7b2cd |
wiki, specifically in the ArtWork page:
|
|
|
d7b2cd |
|
|
|
d7b2cd |
\begin{description}
|
|
|
d7b2cd |
\item[URL:] http://wiki.centos.org/ArtWork
|
|
|
d7b2cd |
\end{description}
|