Remove all trailing whitespace. This is a whitespace commit only, so
translators can ignore this.
This commit is contained in:
Joe Marcus Clarke
parent
e2ccf8da8d
commit
329bb84da0
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=19813
13 changed files with 209 additions and 209 deletions
|
|
@ -1,6 +1,6 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
|
||||
<!ENTITY base CDATA "..">
|
||||
<!ENTITY date "$FreeBSD: www/en/gnome/contact.sgml,v 1.17 2003/08/15 00:01:20 marcus Exp $">
|
||||
<!ENTITY date "$FreeBSD: www/en/gnome/contact.sgml,v 1.18 2003/11/13 00:49:24 adamw Exp $">
|
||||
<!ENTITY title "FreeBSD GNOME Project: Contact Us">
|
||||
<!ENTITY % gnomeincludes SYSTEM "includes.sgml"> %gnomeincludes;
|
||||
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
|
||||
|
|
@ -15,9 +15,9 @@
|
|||
<a href="mailto:freebsd-gnome@FreeBSD.org">freebsd-gnome</a>
|
||||
mailing list. All FreeBSD GNOME users, as well as those who wish to
|
||||
help improve and maintain GNOME on FreeBSD should feel free to
|
||||
<a href="http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-SUBSCRIBE">join</a>.
|
||||
However, you do not have to subscribe if you just want to
|
||||
report a problem or ask for help - just send your message
|
||||
<a href="http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-SUBSCRIBE">join</a>.
|
||||
However, you do not have to subscribe if you just want to
|
||||
report a problem or ask for help - just send your message
|
||||
to <a href="mailto:&email;@FreeBSD.org">&email;@FreeBSD.org</a>.</p>
|
||||
|
||||
<p>All relevant discussions should be carried out in the mailing list,
|
||||
|
|
@ -27,12 +27,12 @@
|
|||
<ul>
|
||||
<li><a href="mailto:adamw@FreeBSD.org">Adam Weinberger</a></li>
|
||||
<li><a href="mailto:bland@FreeBSD.org">Alexander Nedotsukov</a></li>
|
||||
<li><a href="mailto:marcus@FreeBSD.org">Joe Marcus Clarke</a> (AIM: FreeBSDMarcus)</li>
|
||||
<li><a href="mailto:marcus@FreeBSD.org">Joe Marcus Clarke</a> (AIM: FreeBSDMarcus)</li>
|
||||
<li><a href="mailto:pav@FreeBSD.org">Pav Lucistnik</a></li>
|
||||
<li><a href="mailto:sobomax@FreeBSD.org">Maxim Sobolev</a></li>
|
||||
</ul>
|
||||
|
||||
<p>FreeBSD GNOME developers can also be found lurking on IRC.
|
||||
<p>FreeBSD GNOME developers can also be found lurking on IRC.
|
||||
So please join #freebsd-gnome on FreeNode if you would like to discuss
|
||||
GNOME on FreeBSD.</p>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
|
||||
<!ENTITY base CDATA "../..">
|
||||
<!ENTITY date "$FreeBSD: www/en/gnome/docs/bugging.sgml,v 1.11 2003/12/29 03:37:36 marcus Exp $">
|
||||
<!ENTITY date "$FreeBSD: www/en/gnome/docs/bugging.sgml,v 1.12 2004/01/23 02:47:08 viny Exp $">
|
||||
<!ENTITY title "FreeBSD GNOME Project: Reporting a Bug">
|
||||
<!ENTITY % gnomeincludes SYSTEM "../includes.sgml"> %gnomeincludes;
|
||||
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
|
||||
|
|
@ -12,18 +12,18 @@
|
|||
<h2>1. What to report?</h2>
|
||||
|
||||
<p>The rule of the thumb is: report as much information as you
|
||||
can. Even if there is some irrelevant information
|
||||
developers can easily filter it out. On the contrary, the
|
||||
situation is much worse when there is too little information to
|
||||
reliably track down or reproduce the problem - in this case
|
||||
developers have to spend their time guessing and/or asking
|
||||
can. Even if there is some irrelevant information
|
||||
developers can easily filter it out. On the contrary, the
|
||||
situation is much worse when there is too little information to
|
||||
reliably track down or reproduce the problem - in this case
|
||||
developers have to spend their time guessing and/or asking
|
||||
originator of report to send more information.</p>
|
||||
|
||||
<p>There are plenty of examples of totally useless bug reports,
|
||||
something like <i>"Hey, gnomefoo port is broken. I'm running
|
||||
FreeBSD-X.Y. Please fix."</i> Needless to say, that such a report
|
||||
is just a waste of your time, time of the appropriate developer,
|
||||
and network bandwidth. At a bare minimum the report should
|
||||
<p>There are plenty of examples of totally useless bug reports,
|
||||
something like <i>"Hey, gnomefoo port is broken. I'm running
|
||||
FreeBSD-X.Y. Please fix."</i> Needless to say, that such a report
|
||||
is just a waste of your time, time of the appropriate developer,
|
||||
and network bandwidth. At a bare minimum the report should
|
||||
include the following information:</p>
|
||||
|
||||
<ul>
|
||||
|
|
@ -31,16 +31,16 @@
|
|||
<tt>uname -a</tt>).</p></li>
|
||||
<li><p>List of all packages installed on your system.</p></li>
|
||||
<li><p>Your environment (output of <tt>/usr/bin/env</tt>).
|
||||
<li><p>If you are building from ports then the approximate time
|
||||
<li><p>If you are building from ports then the approximate time
|
||||
when you last updated your ports tree.</p></li>
|
||||
<li><p>Information specific for each type of breakage: full log of
|
||||
unsuccessful build in the case when the build of the port is
|
||||
broken, stack trace in the case of a core dump, clear and
|
||||
detailed description of the problem when the application does
|
||||
something unexpected, etc. Try to put yourself into the
|
||||
developer's shoes and in each particular case evaluate what
|
||||
information would be necessary for them to locate the source of
|
||||
the problem. Do not just assume that they already know all
|
||||
unsuccessful build in the case when the build of the port is
|
||||
broken, stack trace in the case of a core dump, clear and
|
||||
detailed description of the problem when the application does
|
||||
something unexpected, etc. Try to put yourself into the
|
||||
developer's shoes and in each particular case evaluate what
|
||||
information would be necessary for them to locate the source of
|
||||
the problem. Do not just assume that they already know all
|
||||
about the problem, but are just too lazy to fix it.</p></li>
|
||||
</ul>
|
||||
|
||||
|
|
@ -73,8 +73,8 @@
|
|||
information.</p>
|
||||
|
||||
<p>If you have a solution or a workaround for the problem then include
|
||||
it into your report as well, even if you are not quite sure that
|
||||
this is a correct fix. If it is not it could still give the
|
||||
it into your report as well, even if you are not quite sure that
|
||||
this is a correct fix. If it is not it could still give the
|
||||
developer an idea about what to look at; and save them some time.
|
||||
</p>
|
||||
|
||||
|
|
@ -88,35 +88,35 @@
|
|||
your solution much faster.
|
||||
</p>
|
||||
|
||||
<p>Once you are sure this is a new problem, there are several ways
|
||||
to report a bug in GNOME running on FreeBSD: you could
|
||||
<p>Once you are sure this is a new problem, there are several ways
|
||||
to report a bug in GNOME running on FreeBSD: you could
|
||||
send a report to the
|
||||
<a href="mailto:&email;@FreeBSD.org">freebsd-gnome mailing
|
||||
list</a>, file a problem report in the
|
||||
<a href="http://www.freebsd.org/support.html#gnats">FreeBSD bug
|
||||
reporting system</a>, send your report to the particular GNOME
|
||||
developers via their
|
||||
<a href="http://bugzilla.gnome.org/">bug tracking system</a>, or
|
||||
<a href="http://bugzilla.gnome.org/">bug tracking system</a>, or
|
||||
any combination of those.<p>
|
||||
|
||||
<p>It is impossible to define guidelines that will clearly tell you
|
||||
where to report in each particular case - you have to use your own
|
||||
<p>It is impossible to define guidelines that will clearly tell you
|
||||
where to report in each particular case - you have to use your own
|
||||
common sense, however some rules follow:</p>
|
||||
|
||||
<ul>
|
||||
<li><p>If the problem is FreeBSD-specific and transient (e.g.
|
||||
checksum mismatch, patch failure, syntax error in port's Makefile
|
||||
<li><p>If the problem is FreeBSD-specific and transient (e.g.
|
||||
checksum mismatch, patch failure, syntax error in port's Makefile
|
||||
etc.) then report to the <a href="mailto:&email;@FreeBSD.org">
|
||||
freebsd-gnome mailing list</a>.</p></li>
|
||||
<li><p>If the problem is clearly not FreeBSD-specific and you have
|
||||
<li><p>If the problem is clearly not FreeBSD-specific and you have
|
||||
no readily available solution then report to the developers of the
|
||||
software directly (for most core GNOME components this means that
|
||||
software directly (for most core GNOME components this means that
|
||||
you need to use their Bugzilla bug tracking system).</p></li>
|
||||
<li><p>If the problem is not FreeBSD-specific, but quite serious
|
||||
and you have a fix available then report both to FreeBSD and
|
||||
author's bug tracking systems, so that the appropriate port will
|
||||
be patched and other users of FreeBSD will be able to benefit
|
||||
from your fix, without the need to wait for the vendor's next
|
||||
<li><p>If the problem is not FreeBSD-specific, but quite serious
|
||||
and you have a fix available then report both to FreeBSD and
|
||||
author's bug tracking systems, so that the appropriate port will
|
||||
be patched and other users of FreeBSD will be able to benefit
|
||||
from your fix, without the need to wait for the vendor's next
|
||||
release.</p></li>
|
||||
</ul>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
|
||||
<!ENTITY base CDATA "../..">
|
||||
<!ENTITY date "$FreeBSD: www/en/gnome/docs/faq2.sgml,v 1.58 2004/01/08 06:42:12 adamw Exp $">
|
||||
<!ENTITY date "$FreeBSD: www/en/gnome/docs/faq2.sgml,v 1.59 2004/01/08 08:26:57 marcus Exp $">
|
||||
<!ENTITY title "FreeBSD GNOME Project: GNOME &gnomever; FAQ">
|
||||
<!ENTITY % gnomeincludes SYSTEM "../includes.sgml"> %gnomeincludes;
|
||||
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
|
||||
|
|
@ -11,15 +11,15 @@
|
|||
<h2>Contents</h2>
|
||||
<ol>
|
||||
<li> <a href="#q1">How do I get GNOME &gnomever; for FreeBSD?</a>
|
||||
<li> <a href="#q2">GNOME &gnomever; is failing to build from ports. What
|
||||
<li> <a href="#q2">GNOME &gnomever; is failing to build from ports. What
|
||||
do I do?</a>
|
||||
<li> <a href="#q3">I installed GNOME &gnomever;, but I am missing
|
||||
<li> <a href="#q3">I installed GNOME &gnomever;, but I am missing
|
||||
application foo. What gives?</a>
|
||||
<li> <a href="#q4">What is the best way to upgrade from GNOME
|
||||
1.4 to GNOME 2?</a>
|
||||
<li> <a href="#q5">What is the best way to upgrade from GNOME
|
||||
2.2 to GNOME &gnomever;?</a>
|
||||
<li> <a href="#q6">How do I keep my GNOME &gnomever; components
|
||||
<li> <a href="#q6">How do I keep my GNOME &gnomever; components
|
||||
and applications up-to-date?</a>
|
||||
<li> <a href="#q7">Can I install GNOME 1.4 applications under
|
||||
GNOME &gnomever;?</a>
|
||||
|
|
@ -30,7 +30,7 @@
|
|||
<li> <a href="#q11">How can I control what fonts are anti-aliased?
|
||||
</a>
|
||||
<li> <a href="#q12">How do I edit my GNOME 2 menus?</a>
|
||||
<li> <a href="#q13">How do I use GTK+ 2 resource settings for
|
||||
<li> <a href="#q13">How do I use GTK+ 2 resource settings for
|
||||
GTK+ 2 applications when not in a GNOME environment?</a>
|
||||
<li> <a href="#q14">How do I configure settings for GNOME 1.4
|
||||
applications under GNOME &gnomever;?</a>
|
||||
|
|
@ -38,14 +38,14 @@
|
|||
How can I fix this?</a>
|
||||
<li> <a href="#q16">How do I add new GDM sessions?</a>
|
||||
</ol>
|
||||
<h2>Full Text </h2>
|
||||
<h2>Full Text </h2>
|
||||
|
||||
<ol>
|
||||
<!-- Q1 -->
|
||||
<li style="padding-bottom: 0.5em"><a name="q1"></a>
|
||||
<p><b>How do I get GNOME &gnomever; for FreeBSD?</b></p>
|
||||
<!-- A1 -->
|
||||
<p>There are two ways to install GNOME &gnomever; on FreeBSD. One way is to use
|
||||
<p>There are two ways to install GNOME &gnomever; on FreeBSD. One way is to use
|
||||
<a href="http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/packages-using.html">
|
||||
packages</a>, and the other way is to use
|
||||
<a href="http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html">
|
||||
|
|
@ -58,11 +58,11 @@
|
|||
|
||||
<tt># pkg_add -r gnome2</tt>
|
||||
|
||||
<p>This will download the latest GNOME &gnomever; packages from the
|
||||
<p>This will download the latest GNOME &gnomever; packages from the
|
||||
FreeBSD FTP site, and proceed to install them on your system.
|
||||
</p>
|
||||
|
||||
<p>To build and install GNOME &gnomever; from ports, you should first
|
||||
<p>To build and install GNOME &gnomever; from ports, you should first
|
||||
<a href="http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html">
|
||||
cvsup</a> the latest ports tree. Then:</p>
|
||||
|
||||
|
|
@ -73,7 +73,7 @@
|
|||
</pre>
|
||||
|
||||
<p>For the best GNOME &gnomever; experience, you should install from
|
||||
ports, after adding the following macros to your
|
||||
ports, after adding the following macros to your
|
||||
<tt>/etc/make.conf</tt> file:</p>
|
||||
|
||||
<pre>
|
||||
|
|
@ -125,25 +125,25 @@ exec gnome-session
|
|||
<li style="padding-bottom: 0.5em"><a name="q2"></a>
|
||||
<p><b>GNOME &gnomever; is failing to build from ports. What do I do?</b></p>
|
||||
<!-- A2 -->
|
||||
<p>The majority of GNOME &gnomever; compilation problems can be solved
|
||||
by making sure all the necessary GNOME &gnomever; components are
|
||||
<p>The majority of GNOME &gnomever; compilation problems can be solved
|
||||
by making sure all the necessary GNOME &gnomever; components are
|
||||
<a href="#q6">up-to-date</a>.</p>
|
||||
|
||||
|
||||
<p>In general, when a GNOME &gnomever; component is not up-to-date,
|
||||
you will see an error similar to the following:</p>
|
||||
|
||||
<pre>
|
||||
checking for libgnomeui-2.0 libbonoboui-2.0 libbonobo-2.0 >= 2.2.1
|
||||
gnome-vfs-2.0 libgnomeprint-2.2 >= 2.3.0 libgnomeprintui-2.2 libglade-2.0...
|
||||
gnome-vfs-2.0 libgnomeprint-2.2 >= 2.3.0 libgnomeprintui-2.2 libglade-2.0...
|
||||
configure: error: Library requirements (libgnomeui-2.0 libbonoboui-2.0
|
||||
libbonobo-2.0 >= 2.2.1 gnome-vfs-2.0 libgnomeprint-2.2 >= 2.3.0 libgnomeprintui-2.2
|
||||
libglade-2.0) not met; consider adjusting the PKG_CONFIG_PATH environment variable
|
||||
if your libraries are in a nonstandard prefix so pkg-config can find them.
|
||||
</pre>
|
||||
|
||||
|
||||
<p>Simply keeping your ports tree <a href="#q6">up-to-date</a> will
|
||||
prevent these errors.</p>
|
||||
|
||||
|
||||
<p>If the <tt>pkg-config</tt> program is out-of-date, you may see
|
||||
a configure error similar to the following:</p>
|
||||
|
||||
|
|
@ -153,11 +153,11 @@ configure: error: *** pkg-config too old; version 0.14 or better required.
|
|||
|
||||
<p>While this may be buried in some other text, the error is
|
||||
very straight-forward: you need to upgrade pkg-config.
|
||||
The pkg-config application is found in the
|
||||
The pkg-config application is found in the
|
||||
<tt>devel/pkgconfig</tt> port. By updating this port to
|
||||
the latest version, this error will go away.</p>
|
||||
|
||||
<p>You may see compiler errors relating to pthreads
|
||||
|
||||
<p>You may see compiler errors relating to pthreads
|
||||
(&posix; threads), such as:</p>
|
||||
|
||||
<pre>
|
||||
|
|
@ -172,9 +172,9 @@ options _KPOSIX_PRIORITY_SCHEDULING
|
|||
</pre>
|
||||
|
||||
<p>If you are tracking -stable or -current, make sure that you
|
||||
do <b>not</b> have <tt>NOLIBC_R</tt> set in
|
||||
do <b>not</b> have <tt>NOLIBC_R</tt> set in
|
||||
<tt>/etc/make.conf</tt>. If you do, remove it, then rebuild world.
|
||||
If you still have trouble, please send email to
|
||||
If you still have trouble, please send email to
|
||||
<a href="mailto:&email;@FreeBSD.org">
|
||||
&email;@FreeBSD.org</a> with the output of the failed compilation.
|
||||
It is also helpful to include the config.log from the port's
|
||||
|
|
@ -203,9 +203,9 @@ options _KPOSIX_PRIORITY_SCHEDULING
|
|||
<!-- A3 -->
|
||||
<p>Only the core desktop is included in the
|
||||
<tt>gnome2</tt> package. Here are some other GNOME
|
||||
meta-ports that offer convenient groupings of popular GNOME 2
|
||||
meta-ports that offer convenient groupings of popular GNOME 2
|
||||
software.</p>
|
||||
|
||||
|
||||
<ul>
|
||||
<li>The <b>GNOME 2 Fifth Toe</b> (<tt>x11/gnome2-fifth-toe</tt>)
|
||||
consists of stable GNOME 2 applications that many users
|
||||
|
|
@ -214,12 +214,12 @@ options _KPOSIX_PRIORITY_SCHEDULING
|
|||
messenger applications, and music and multimedia players</li>
|
||||
|
||||
<li>The <b>GNOME 2 Hacker Tools</b>
|
||||
(<tt>devel/gnome2-hacker-tools</tt>) consists of applications
|
||||
developers would need to create and maintain GNOME software
|
||||
projects. This includes IDEs, interface builders, ``hacker''
|
||||
(<tt>devel/gnome2-hacker-tools</tt>) consists of applications
|
||||
developers would need to create and maintain GNOME software
|
||||
projects. This includes IDEs, interface builders, ``hacker''
|
||||
editors, and code generation tools.</li>
|
||||
|
||||
<li>The <b>GNOME 2 Office</b> (<tt>editors/gnome2-office</tt>)
|
||||
<li>The <b>GNOME 2 Office</b> (<tt>editors/gnome2-office</tt>)
|
||||
consists of applications that are commonly found in office or
|
||||
productivity suites. This includes a spreadsheet application,
|
||||
word processor, project management application, database
|
||||
|
|
@ -234,7 +234,7 @@ options _KPOSIX_PRIORITY_SCHEDULING
|
|||
</pre>
|
||||
|
||||
<p>For example, to install the GNOME 2 Fifth Toe from packages:</p>
|
||||
|
||||
|
||||
<pre>
|
||||
# pkg_add -r gnome2-fifth-toe
|
||||
</pre>
|
||||
|
|
@ -267,11 +267,11 @@ options _KPOSIX_PRIORITY_SCHEDULING
|
|||
the GNOME site. Make sure your GNOME 1.4 ports are
|
||||
up-to-date, and then remove the following GNOME 1.4 packages from
|
||||
the system:</p>
|
||||
|
||||
|
||||
<pre>
|
||||
gnomecore
|
||||
sawfish
|
||||
gnomeapplets
|
||||
gnomeapplets
|
||||
gnomemedia
|
||||
gtop
|
||||
libgtop
|
||||
|
|
@ -287,7 +287,7 @@ eog
|
|||
ggv
|
||||
</pre>
|
||||
|
||||
<p>After those packages are removed, you can build GNOME &gnomever; as per
|
||||
<p>After those packages are removed, you can build GNOME &gnomever; as per
|
||||
the <a href="#q1">instructions listed above</a>.</p>
|
||||
|
||||
</li>
|
||||
|
|
@ -312,7 +312,7 @@ to run the above command after each step below)
|
|||
|
||||
<!-- Q6 -->
|
||||
<li style="padding-bottom: 0.5em"><a name="q6"></a>
|
||||
<p><b>How do I keep my GNOME &gnomever; components and applications
|
||||
<p><b>How do I keep my GNOME &gnomever; components and applications
|
||||
up-to-date?</b></p>
|
||||
<!-- A6 -->
|
||||
<p>You are emphatically encouraged to use <tt>portupgrade</tt> --
|
||||
|
|
@ -366,7 +366,7 @@ to run the above command after each step below)
|
|||
<li style="padding-bottom: 0.5em"><a name="q8"></a>
|
||||
<p><b>Where can I get more themes for GNOME &gnomever;?</b></p>
|
||||
<!-- A8 -->
|
||||
<p>The website <a href="http://art.gnome.org">
|
||||
<p>The website <a href="http://art.gnome.org">
|
||||
art.gnome.org</a> has been setup as a general GNOME theme
|
||||
repository. They offer some gtk+-2, metacity, sawfish,
|
||||
nautilus, icon, and gdm themes, as well as some backgrounds.</p>
|
||||
|
|
@ -376,7 +376,7 @@ to run the above command after each step below)
|
|||
themes for GNOME 2 as well as KDE and quite a few window
|
||||
managers.
|
||||
</p>
|
||||
|
||||
|
||||
<p>Freshmeat.net has a themes archive at
|
||||
<a href="http://themes.freshmeat.net">themes.freshmeat.net</a>,
|
||||
which contains themes and backgrounds for many window managers,
|
||||
|
|
@ -385,7 +385,7 @@ to run the above command after each step below)
|
|||
</p>
|
||||
|
||||
<p>A good site for some cool GNOME icons (some stock, some new)
|
||||
is jimmac's <a href="http://jimmac.musichall.cz/ikony.php3">
|
||||
is jimmac's <a href="http://jimmac.musichall.cz/ikony.php3">
|
||||
Icons</a> site.</p>
|
||||
|
||||
<p>See the instructions on the website for installing the themes.
|
||||
|
|
@ -397,9 +397,9 @@ to run the above command after each step below)
|
|||
<li style="padding-bottom: 0.5em"><a name="q9"></a>
|
||||
<p><b>What window managers work well with GNOME &gnomever;?</b></p>
|
||||
<!-- A9 -->
|
||||
<p>The <tt>gnome2</tt> meta-port installs the
|
||||
<p>The <tt>gnome2</tt> meta-port installs the
|
||||
metacity window manager by default. Another popular window
|
||||
manager that works well with GNOME &gnomever; is
|
||||
manager that works well with GNOME &gnomever; is
|
||||
<a href="http://sawmill.sourceforge.net/">sawfish</a>. Sawfish
|
||||
can be found in <tt>x11-wm/sawfish2</tt>.</p>
|
||||
|
||||
|
|
@ -412,7 +412,7 @@ gnome-session-save --gui
|
|||
</pre>
|
||||
<p>The <tt>gnome-session-save</tt> is important. Without it, the
|
||||
window manager will revert back to the one previously configured
|
||||
upon next login. To switch back, simply reverse sawfish and
|
||||
upon next login. To switch back, simply reverse sawfish and
|
||||
metacity.</p>
|
||||
|
||||
<p>If you have gotten the GNOME &gnomever; desktop working under an
|
||||
|
|
@ -425,31 +425,31 @@ gnome-session-save --gui
|
|||
<li style="padding-bottom: 0.5em"><a name="q10"></a>
|
||||
<p><b>Does GNOME &gnomever; support anti-aliased fonts?</b></p>
|
||||
<!-- A10 -->
|
||||
<p>Yes! Anti-aliasing requires XFree86 4.x with
|
||||
<p>Yes! Anti-aliasing requires XFree86 4.x with
|
||||
freetype2 support. To add freetype2 support to X, make
|
||||
sure you have the following modules loaded in your
|
||||
sure you have the following modules loaded in your
|
||||
XF86Config file under the Modules section:</p>
|
||||
|
||||
<pre>
|
||||
Load "freetype"
|
||||
Load "type1"
|
||||
</pre>
|
||||
|
||||
|
||||
<p>Then, simply check out the Fonts capplet under
|
||||
Applications->Desktop Preferences. If you want a good set
|
||||
of TrueType starter fonts, install the
|
||||
of TrueType starter fonts, install the
|
||||
<tt>x11-fonts/webfonts</tt> port.</p>
|
||||
|
||||
<p>Sometimes, after adding new fonts to the system, it is
|
||||
necessary to teach fontconfig about them. If you find that
|
||||
newly added fonts are not made available even after
|
||||
newly added fonts are not made available even after
|
||||
restarting GNOME 2, run the following command as root:</p>
|
||||
|
||||
<pre>
|
||||
# fc-cache -f -v
|
||||
</pre>
|
||||
|
||||
<p>If you have any questions, please send them to
|
||||
<p>If you have any questions, please send them to
|
||||
<a href="mailto:&email;@FreeBSD.org">&email;@FreeBSD.org</a>.
|
||||
</p>
|
||||
</li>
|
||||
|
|
@ -458,7 +458,7 @@ Load "type1"
|
|||
<li style="padding-bottom: 0.5em"><a name="q11"></a>
|
||||
<p><b>How can I control what fonts are anti-aliased?</b></p>
|
||||
<!-- A11 -->
|
||||
<p>GNOME &gnomever; makes use of Xft and fontconfig to handle
|
||||
<p>GNOME &gnomever; makes use of Xft and fontconfig to handle
|
||||
anti-aliasing. Fontconfig is a very powerful XML-based
|
||||
font configuration package. You can create a
|
||||
<tt>~/.fonts.conf</tt> file that controls virtually
|
||||
|
|
@ -493,7 +493,7 @@ Load "type1"
|
|||
want to edit any menu other than Favorites, you must be
|
||||
root.</p>
|
||||
|
||||
<p>To edit the menus, launch Nautilus, and enter the URL
|
||||
<p>To edit the menus, launch Nautilus, and enter the URL
|
||||
<b>applications:///</b>. From there you should be able to edit
|
||||
your entire application menu.</p>
|
||||
</li>
|
||||
|
|
@ -520,7 +520,7 @@ Load "type1"
|
|||
|
||||
<ol>
|
||||
<li> If you have any theme engine references, you will have
|
||||
to make sure there is a corresponding GTK+ 2 theme engine.
|
||||
to make sure there is a corresponding GTK+ 2 theme engine.
|
||||
Otherwise, remove the engine entries.</li>
|
||||
<li> The default font specification should be outside of
|
||||
any <tt>style</tt> blocks and should be specified with
|
||||
|
|
@ -556,7 +556,7 @@ Load "type1"
|
|||
permissions on the device nodes allow write access.
|
||||
Nautilus-cd-burner talks to CD/DVD burners through the
|
||||
SCSI CAM subsystem. Therefore, you must make sure
|
||||
you have the following configured in your kernel:</p>
|
||||
you have the following configured in your kernel:</p>
|
||||
|
||||
<pre>
|
||||
device scbus
|
||||
|
|
@ -586,12 +586,12 @@ device atapicam
|
|||
|
||||
<p>The devices in parentheses at the end are important. You
|
||||
must make sure the <tt>/dev</tt> entries for those devices
|
||||
are writable by the users that will be using
|
||||
are writable by the users that will be using
|
||||
nautilus-cd-burner. In addition to those devices,
|
||||
<tt>/dev/xpt*</tt> must also be writable to your
|
||||
nautilus-cd-burner users. The following
|
||||
<tt>/dev/xpt*</tt> must also be writable to your
|
||||
nautilus-cd-burner users. The following
|
||||
<tt>/etc/devfs.conf</tt> configuration will achieve the
|
||||
desired results given the above devlist (<b>NB:</b>
|
||||
desired results given the above devlist (<b>NB:</b>
|
||||
<tt>devfs.conf</tt> is only supported on FreeBSD 5.x):</p>
|
||||
|
||||
<pre>
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
|
||||
<!ENTITY base CDATA "../..">
|
||||
<!ENTITY date "$FreeBSD: www/en/gnome/docs/gnome2_porting.sgml,v 1.9 2004/01/07 23:38:16 adamw Exp $">
|
||||
<!ENTITY date "$FreeBSD: www/en/gnome/docs/gnome2_porting.sgml,v 1.10 2004/01/07 23:45:48 adamw Exp $">
|
||||
<!ENTITY title "FreeBSD GNOME Project: GNOME 2 Components">
|
||||
<!ENTITY % gnomeincludes SYSTEM "../includes.sgml"> %gnomeincludes;
|
||||
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
|
||||
|
|
@ -92,13 +92,13 @@
|
|||
<td><tt>x11-toolkits/gtk20</tt></td>
|
||||
<td><tt>atk pango</tt></td>
|
||||
</tr>
|
||||
|
||||
|
||||
<tr>
|
||||
<td><tt>gtksourceview</tt></td>
|
||||
<td><tt>x11-toolkits/gtksourceview</tt></td>
|
||||
<td><tt>libgnome libgnomeprintui</tt></td>
|
||||
</tr>
|
||||
|
||||
|
||||
<tr>
|
||||
<td><tt>libartlgpl2</tt></td>
|
||||
<td><tt>graphics/libartlgpl2</tt></td>
|
||||
|
|
@ -110,7 +110,7 @@
|
|||
<td><tt>devel/libbonobo</tt></td>
|
||||
<td><tt>libxml2 orbit2</tt></td>
|
||||
</tr>
|
||||
|
||||
|
||||
<tr>
|
||||
<td><tt>libbonoboui</tt></td>
|
||||
<td><tt>x11-toolkits/libbonoboui</tt></td>
|
||||
|
|
@ -134,7 +134,7 @@
|
|||
<td><tt>devel/libglade2</tt></td>
|
||||
<td><tt>libxml2 gtk20</tt></td>
|
||||
</tr>
|
||||
|
||||
|
||||
<tr>
|
||||
<td><tt>libgnome</tt></td>
|
||||
<td><tt>x11/libgnome</tt></td>
|
||||
|
|
@ -188,7 +188,7 @@
|
|||
<td><tt>devel/libIDL</tt></td>
|
||||
<td><tt>glib20</tt></td>
|
||||
</tr>
|
||||
|
||||
|
||||
<tr>
|
||||
<td><tt>libwnck</tt></td>
|
||||
<td><tt>x11-toolkits/libwnck</tt></td>
|
||||
|
|
@ -206,13 +206,13 @@
|
|||
<td><tt>textproc/libxml2</tt></td>
|
||||
<td><tt>pkgconfig</tt></td>
|
||||
</tr>
|
||||
|
||||
|
||||
<tr>
|
||||
<td><tt>libxslt</tt></td>
|
||||
<td><tt>textproc/libxslt</tt></td>
|
||||
<td><tt>libxml2</tt></td>
|
||||
</tr>
|
||||
|
||||
|
||||
<tr>
|
||||
<td><tt>libzvt</tt></td>
|
||||
<td><tt>x11-toolkits/libzvt</tt></td>
|
||||
|
|
@ -224,7 +224,7 @@
|
|||
<td><tt>net/linc</tt></td>
|
||||
<td><tt>glib20</tt></td>
|
||||
</tr>
|
||||
|
||||
|
||||
<tr>
|
||||
<td><tt>nautilus2</tt></td>
|
||||
<td><tt>x11-fm/nautilus</tt></td>
|
||||
|
|
@ -242,13 +242,13 @@
|
|||
<td><tt>devel/ORBit2</tt></td>
|
||||
<td><tt>libidl</tt></td>
|
||||
</tr>
|
||||
|
||||
|
||||
<tr>
|
||||
<td><tt>pango</tt></td>
|
||||
<td><tt>x11-toolkits/pango</tt></td>
|
||||
<td><tt>glib20</tt></td>
|
||||
</tr>
|
||||
|
||||
|
||||
<tr>
|
||||
<td><tt>vte</tt></td>
|
||||
<td><tt>x11-toolkits/vte</tt></td>
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
|
||||
<!ENTITY base CDATA "../..">
|
||||
<!ENTITY date "$FreeBSD: www/en/gnome/docs/gnome_porting.sgml,v 1.9 2004/01/07 23:45:48 adamw Exp $">
|
||||
<!ENTITY date "$FreeBSD: www/en/gnome/docs/gnome_porting.sgml,v 1.10 2004/01/08 06:20:39 adamw Exp $">
|
||||
<!ENTITY title "FreeBSD GNOME Project: GNOME Desktop-Independent Components">
|
||||
<!ENTITY % gnomeincludes SYSTEM "../includes.sgml"> %gnomeincludes;
|
||||
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
|
||||
|
|
@ -40,7 +40,7 @@
|
|||
<tr>
|
||||
<td><tt>gnomehier</tt></td>
|
||||
<td colspan="2"><tt>gnomehier</tt> installs all the
|
||||
directories needed for both the GNOME 1 and 2 desktops.
|
||||
directories needed for both the GNOME 1 and 2 desktops.
|
||||
Only include this option if your port calls <tt>@dirrm</tt>
|
||||
on one of the directories listed in the plist for
|
||||
<tt>gnomehier</tt>.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
|
||||
<!ENTITY base CDATA "../..">
|
||||
<!ENTITY date "$FreeBSD: www/en/gnome/docs/knownissues.sgml,v 1.8 2003/09/30 08:29:18 marcus Exp $">
|
||||
<!ENTITY date "$FreeBSD: www/en/gnome/docs/knownissues.sgml,v 1.9 2003/10/21 22:21:39 adamw Exp $">
|
||||
<!ENTITY title "FreeBSD GNOME Project: Known Issues with GNOME &gnomever; on FreeBSD">
|
||||
<!ENTITY % gnomeincludes SYSTEM "../includes.sgml"> %gnomeincludes;
|
||||
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
|
||||
|
|
@ -9,11 +9,11 @@
|
|||
<html>
|
||||
&header;
|
||||
|
||||
<p>Below is a list of known issues with GNOME &gnomever; that are
|
||||
<p>Below is a list of known issues with GNOME &gnomever; that are
|
||||
specific to FreeBSD. These are not the only known issues,
|
||||
however. Please familiarize yourself with the GNOME &gnomever;
|
||||
<a href="http://www.gnome.org/start/&gnomever;/notes/">
|
||||
release notes</a> which contains a
|
||||
release notes</a> which contains a
|
||||
<a href="http://www.gnome.org/start/&gnomever;/notes/rnknownissues.html">
|
||||
list</a> of known issues that affect all platforms.</p>
|
||||
|
||||
|
|
@ -23,11 +23,11 @@
|
|||
<a href="http://www.freebsd.org/gnome/docs/faq2.html#q5">
|
||||
instructions</a> for updating to GNOME &gnomever;. This may
|
||||
still produce errors, however. You may have to re-run
|
||||
<tt>pkgdb -F</tt> after each step. If you continue to
|
||||
<tt>pkgdb -F</tt> after each step. If you continue to
|
||||
encounter errors after following the upgrade instructions,
|
||||
log the entire upgrade procedure (you can use the <tt>-l</tt>
|
||||
option to <tt>portupgrade</tt> to accomplish this).
|
||||
<b>Compress</b> and send the log to
|
||||
option to <tt>portupgrade</tt> to accomplish this).
|
||||
<b>Compress</b> and send the log to
|
||||
<a href="mailto:&email;@FreeBSD.org">&email;@FreeBSD.org</a>.
|
||||
</p>
|
||||
|
||||
|
|
@ -48,17 +48,17 @@
|
|||
|
||||
<p> gstreamer-0.6.3 doesn't play nice with rhythmbox. It is
|
||||
recommended you build rhythmbox with <tt>-DWITH_XINE</tt> for
|
||||
now. (<b>UPDATE:</b> As of gstreamer-plugins-0.6.3_1, this
|
||||
now. (<b>UPDATE:</b> As of gstreamer-plugins-0.6.3_1, this
|
||||
problem has been resolved.)
|
||||
</p>
|
||||
|
||||
<h3>4. GDM crashes on startup</h3>
|
||||
|
||||
<p>GDM may crash on startup, especially on 5.1-RELEASE and
|
||||
earlier. All GDM users need to copy
|
||||
earlier. All GDM users need to copy
|
||||
<tt>/usr/X11R6/etc/gdm/factory-gdm.conf</tt> over
|
||||
<tt>/usr/X11R6/etc/gdm/gdm.conf</tt>. The old
|
||||
config version from GNOME 2.2 will not work. Users of
|
||||
config version from GNOME 2.2 will not work. Users of
|
||||
5.1-RELEASE and earlier need to read the <tt>pkg-message</tt>
|
||||
that comes with the GDM2 port/package on how to patch OpenPAM
|
||||
to work with GDM2.</p>
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
|
||||
<!ENTITY base CDATA "../..">
|
||||
<!ENTITY date "$FreeBSD: www/en/gnome/docs/porting.sgml,v 1.35 2003/12/28 03:06:00 adamw Exp $">
|
||||
<!ENTITY date "$FreeBSD: www/en/gnome/docs/porting.sgml,v 1.36 2004/01/07 23:38:16 adamw Exp $">
|
||||
<!ENTITY title "FreeBSD GNOME Project: How To Make a Port">
|
||||
<!ENTITY % gnomeincludes SYSTEM "../includes.sgml"> %gnomeincludes;
|
||||
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
|
||||
|
|
@ -10,7 +10,7 @@
|
|||
|
||||
<p>This document assumes that you already know how the port system works,
|
||||
and therefore only provides GNOME-specific hints and tips. General
|
||||
instructions can be found in the
|
||||
instructions can be found in the
|
||||
<a href="http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/index.html">FreeBSD Porter's Handbook</a>.
|
||||
</p>
|
||||
|
||||
|
|
@ -62,8 +62,8 @@ USE_GNOME= gtk12
|
|||
list to make sure your port uses all relevant components.</p>
|
||||
<!-- end questionable section -->
|
||||
|
||||
<p>Once you have finished with your port, it is a good idea to
|
||||
verify that your port depends on the correct list of components.
|
||||
<p>Once you have finished with your port, it is a good idea to
|
||||
verify that your port depends on the correct list of components.
|
||||
To see a list of what packages your port will actually require,
|
||||
use the command <tt>make package-depends</tt> from within
|
||||
your port's directory.</p>
|
||||
|
|
@ -91,7 +91,7 @@ gtk+-2.0 >= 2.0.0 gail libwnck-1.0 esound... yes
|
|||
There are a number of other such redundancies that can be eliminated
|
||||
from this list.</p>
|
||||
|
||||
<p>For the above list (taken from <tt>sysutils/gok</tt>), the
|
||||
<p>For the above list (taken from <tt>sysutils/gok</tt>), the
|
||||
following is defined in the <tt>Makefile</tt>:
|
||||
|
||||
<pre>
|
||||
|
|
@ -113,7 +113,7 @@ USE_GNOME= gnomehack gnomeprefix libgnomeui atspi libwnck
|
|||
<p>What this means for you, as an application porter, is simply that
|
||||
you should not add <tt>GNOME 1</tt>-specific applications to the
|
||||
ports tree.</p>
|
||||
|
||||
|
||||
<p>If you wish to determine which version of the GNOME desktop
|
||||
environment is present on a user's machine, you can check the value
|
||||
of <b>GNOME_DESKTOP_VERSION</b>. This variable is set to either
|
||||
|
|
@ -121,7 +121,7 @@ USE_GNOME= gnomehack gnomeprefix libgnomeui atspi libwnck
|
|||
<tt>GNOME 1</tt> or <tt>GNOME 2</tt> desktop is installed.</p>
|
||||
|
||||
<h2>Optional GNOME Dependencies</h2>
|
||||
<p>If your port can optionally use GNOME, you must set
|
||||
<p>If your port can optionally use GNOME, you must set
|
||||
<tt>WANT_GNOME= yes</tt> in your Makefile, then check to see if
|
||||
<tt>HAVE_GNOME</tt> is set for each component from the list
|
||||
above that your port can use. Since this is a conditional
|
||||
|
|
@ -147,29 +147,29 @@ WANT_GNOME= yes
|
|||
</pre>
|
||||
|
||||
<p>Here, <tt>WANT_GNOME</tt> tells the ports system
|
||||
to check for the existence of the various GNOME components
|
||||
to check for the existence of the various GNOME components
|
||||
listed above. For each component found, its name is appended
|
||||
to <tt>HAVE_GNOME</tt>. Since this port can use <tt>gnomepanel</tt>,
|
||||
we check <tt>HAVE_GNOME</tt> to see if it contains
|
||||
<tt>gnomepanel</tt> (for more on the :M<tt>pattern</tt> make syntax,
|
||||
please refer to the
|
||||
to <tt>HAVE_GNOME</tt>. Since this port can use <tt>gnomepanel</tt>,
|
||||
we check <tt>HAVE_GNOME</tt> to see if it contains
|
||||
<tt>gnomepanel</tt> (for more on the :M<tt>pattern</tt> make syntax,
|
||||
please refer to the
|
||||
<a href="http://www.freebsd.org/cgi/man.cgi?query=make&apropos=0&sektion=0&manpath=FreeBSD+4.6-stable&format=html">make(1)</a> manpage).
|
||||
If <tt>gnomepanel</tt> is found, then it is added the list of
|
||||
<tt>USE_GNOME</tt> dependencies, and the port-specific
|
||||
<tt>USE_GNOME</tt> dependencies, and the port-specific
|
||||
<tt>--with-gnome</tt> <tt>CONFIGURE_ARG</tt> is passed.
|
||||
In an old GNOME infrastructure, <tt>PKGNAMESUFFIX</tt> was
|
||||
automatically adjusted by the proper <tt>USE_*</tt> macro.
|
||||
Now it is up to the individual porter to do this.
|
||||
Our example port appends <tt>-gnome</tt> to the port name
|
||||
to indicate it has been built with GNOME support. The same is
|
||||
true for the <tt>DATADIR</tt> <tt>PLIST_SUB</tt>. The
|
||||
to indicate it has been built with GNOME support. The same is
|
||||
true for the <tt>DATADIR</tt> <tt>PLIST_SUB</tt>. The
|
||||
individual porter must decide when do the <tt>DATADIR</tt>
|
||||
substitution. A good rule of thumb is to add the <tt>DATADIR</tt>
|
||||
<tt>PLIST_SUB</tt> when using the <tt>gnomeprefix</tt>
|
||||
component.
|
||||
component.
|
||||
</p>
|
||||
|
||||
<p><b>Note:</b> You cannot add extra default <tt>USE_GNOME</tt>
|
||||
<p><b>Note:</b> You cannot add extra default <tt>USE_GNOME</tt>
|
||||
components after the <tt>.include <bsd.port.pre.mk></tt>.
|
||||
That is, the following is <font color="#FF0000"><b>wrong</b>
|
||||
</font>:</p>
|
||||
|
|
@ -211,13 +211,13 @@ WANT_GNOME= yes
|
|||
|
||||
<p>A large number of GNOME applications (especially GNOME 2
|
||||
applications) install Open Source Metadata Framework (OMF)
|
||||
files which contain the help file information for those
|
||||
applications. These OMF files require special processing
|
||||
files which contain the help file information for those
|
||||
applications. These OMF files require special processing
|
||||
by ScrollKeeper in order for applications like Yelp to
|
||||
find help documentation. In order to accomplish proper
|
||||
find help documentation. In order to accomplish proper
|
||||
registry of these OMF files when installing GNOME applications
|
||||
from packages, you should make sure your port's
|
||||
<tt>pkg-plist</tt> has the following for <em>each</em> OMF file
|
||||
from packages, you should make sure your port's
|
||||
<tt>pkg-plist</tt> has the following for <em>each</em> OMF file
|
||||
listed.</p>
|
||||
|
||||
<pre>
|
||||
|
|
@ -246,11 +246,11 @@ WANT_GNOME= yes
|
|||
<h2>Libtool Issues</h2>
|
||||
|
||||
<p>Most, if not all, GNOME applications depend on GNU's libtool.
|
||||
They also use the GNU configure system. If your port installs
|
||||
They also use the GNU configure system. If your port installs
|
||||
shared libraries, you should add <tt>USE_LIBTOOL= yes</tt> to
|
||||
your port's Makefile. This takes care of most of the libtool
|
||||
requirements, but will not prevent things such as .la files
|
||||
from being installed. To ensure a proper shared library
|
||||
from being installed. To ensure a proper shared library
|
||||
installation, also consider adding the following line to your
|
||||
port's <tt>configure</tt> script directly below the line
|
||||
<tt>LIBTOOL_DEPS="$ac_aux_dir/ltmain.sh"</tt>:</p>
|
||||
|
|
@ -258,9 +258,9 @@ WANT_GNOME= yes
|
|||
<pre>
|
||||
$ac_aux_dir/ltconfig $LIBTOOL_DEPS
|
||||
</pre>
|
||||
|
||||
|
||||
<p>This prevents the installation of .la files and
|
||||
ensures that <tt>${PTHREAD_LIBS}</tt> will be passed to the
|
||||
ensures that <tt>${PTHREAD_LIBS}</tt> will be passed to the
|
||||
linker.</p>
|
||||
<!-- End GNOME libtool -->
|
||||
|
||||
|
|
@ -268,8 +268,8 @@ $ac_aux_dir/ltconfig $LIBTOOL_DEPS
|
|||
<h2>Distfiles</h2>
|
||||
|
||||
<p>To separate GNOME 2 distfiles from the GNOME 1 distfiles, and to
|
||||
keep the distfiles directory clean, GNOME 1 ports that
|
||||
download their distfiles from <tt>${MASTER_SITE_GNOME}</tt> must
|
||||
keep the distfiles directory clean, GNOME 1 ports that
|
||||
download their distfiles from <tt>${MASTER_SITE_GNOME}</tt> must
|
||||
add the following to their
|
||||
Makefile:</p>
|
||||
|
||||
|
|
@ -277,15 +277,15 @@ $ac_aux_dir/ltconfig $LIBTOOL_DEPS
|
|||
DIST_SUBDIR= gnome
|
||||
</pre>
|
||||
|
||||
<p>GNOME 2 ports that download their distfiles from
|
||||
<p>GNOME 2 ports that download their distfiles from
|
||||
<tt>${MASTER_SITE_GNOME}</tt> must include the following in their
|
||||
Makefile:</p>
|
||||
|
||||
|
||||
<pre>
|
||||
DIST_SUBDIR= gnome2
|
||||
</pre>
|
||||
|
||||
<p>Some GNOME distfiles come in both tar gzip as well as tar bzip2
|
||||
<p>Some GNOME distfiles come in both tar gzip as well as tar bzip2
|
||||
format. To save time when downloading distfiles over slow links,
|
||||
you should use the bzip2 distfiles whenever possible. To do this,
|
||||
add the following to your port's Makefile:</p>
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
|
||||
<!ENTITY base CDATA "../..">
|
||||
<!ENTITY date "$FreeBSD: www/en/gnome/docs/volunteer.sgml,v 1.6 2003/08/28 19:09:04 marcus Exp $">
|
||||
<!ENTITY date "$FreeBSD: www/en/gnome/docs/volunteer.sgml,v 1.7 2003/09/08 23:35:51 adamw Exp $">
|
||||
<!ENTITY title "FreeBSD GNOME Project: How To Help">
|
||||
<!ENTITY % gnomeincludes SYSTEM "../includes.sgml"> %gnomeincludes;
|
||||
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
|
||||
|
|
@ -15,24 +15,24 @@
|
|||
|
||||
<ul>
|
||||
<li>
|
||||
<p>Test existing <a href="../../ports/gnome.html">ports</a>, and
|
||||
<p>Test existing <a href="../../ports/gnome.html">ports</a>, and
|
||||
<a href="bugging.html">report bugs</a>.</p></li>
|
||||
<li>
|
||||
<p>Regularly install GNOME from packages, and report any problems
|
||||
with the install or the functionality.</p></li>
|
||||
<li>
|
||||
<p>Find GNOME applications not yet ported to FreeBSD, and
|
||||
<p>Find GNOME applications not yet ported to FreeBSD, and
|
||||
work on porting them over.</p></li>
|
||||
<li>
|
||||
<p><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-SUBSCRIBE">
|
||||
Subscribe</a> to the freebsd-gnome mailing list, and help
|
||||
Subscribe</a> to the freebsd-gnome mailing list, and help
|
||||
answer users' questions.</p></li>
|
||||
<li>
|
||||
<p>Take patches and feedback from GNOME-related FreeBSD PRs
|
||||
back to GNOME authors so that the patches can be integrated
|
||||
<p>Take patches and feedback from GNOME-related FreeBSD PRs
|
||||
back to GNOME authors so that the patches can be integrated
|
||||
into the next release of the application.</p></li>
|
||||
<li>
|
||||
<p>Proofread the FreeBSD GNOME <a href="../">project pages</a>,
|
||||
<p>Proofread the FreeBSD GNOME <a href="../">project pages</a>,
|
||||
and offer feedback and updates.</p></li>
|
||||
</ul>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
<?xml version="1.0" encoding="ISO-8859-1" ?>
|
||||
|
||||
<!-- $FreeBSD: www/en/gnome/includes.xsl,v 1.5 2003/09/20 18:53:02 marcus Exp $ -->
|
||||
<!-- $FreeBSD: www/en/gnome/includes.xsl,v 1.6 2003/12/27 23:15:32 adamw Exp $ -->
|
||||
|
||||
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
|
||||
|
||||
|
|
@ -16,11 +16,11 @@
|
|||
2.5
|
||||
</xsl:variable>
|
||||
|
||||
<xsl:variable name="author">
|
||||
<a>
|
||||
<xsl:attribute name="href">
|
||||
<xsl:value-of select="concat($base, '/gnome/contact.html')"/>
|
||||
</xsl:attribute>
|
||||
<xsl:variable name="author">
|
||||
<a>
|
||||
<xsl:attribute name="href">
|
||||
<xsl:value-of select="concat($base, '/gnome/contact.html')"/>
|
||||
</xsl:attribute>
|
||||
<xsl:value-of select="'freebsd-gnome'"/>@FreeBSD.org</a><br/><xsl:copy-of select="$copyright"/>
|
||||
</xsl:variable>
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
<!-- Simple schema for FreeBSD Project news.
|
||||
|
||||
Divide time in to <year>, <month>, and <day> elements, each of which
|
||||
Divide time in to <year>, <month>, and <day> elements, each of which
|
||||
has a <name>.
|
||||
|
||||
each <day> element contains one or more <event> elements.
|
||||
|
|
@ -14,14 +14,14 @@
|
|||
or one of the mirrors.
|
||||
|
||||
Use the <title> element if the <p> content is lengthy. When generating
|
||||
synopses of this information (e.g., for syndication using RDF files),
|
||||
synopses of this information (e.g., for syndication using RDF files),
|
||||
the contents of <title> will be preferred over <p>.
|
||||
-->
|
||||
|
||||
<news>
|
||||
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
|
||||
<cvs:keyword name="freebsd">
|
||||
$FreeBSD: www/en/gnome/news.xml,v 1.53 2003/12/14 16:20:40 marcus Exp $
|
||||
$FreeBSD: www/en/gnome/news.xml,v 1.54 2004/01/06 17:36:56 marcus Exp $
|
||||
</cvs:keyword>
|
||||
</cvs:keywords>
|
||||
|
||||
|
|
@ -39,9 +39,9 @@
|
|||
<p>The GNOME 2.5.2 desktop, "You want me to blow on
|
||||
your toes?" release, is now available for FreeBSD.
|
||||
To accompany this release, the FreeBSD GNOME
|
||||
team has setup an
|
||||
<a href="/gnome/docs/develfaq.html">FAQ</a> on how to
|
||||
track the GNOME development branches. Please read
|
||||
team has setup an
|
||||
<a href="/gnome/docs/develfaq.html">FAQ</a> on how to
|
||||
track the GNOME development branches. Please read
|
||||
that to familiarize yourself with what is involved.
|
||||
This release can be checked out from the
|
||||
<a href="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi">MarcusCom CVS repository</a>.
|
||||
|
|
@ -64,7 +64,7 @@
|
|||
<event>
|
||||
<title>GNOME 2.5.1 available for FreeBSD</title>
|
||||
|
||||
<p>The GNOME 2.5.1 desktop, "Hey, at least I'm
|
||||
<p>The GNOME 2.5.1 desktop, "Hey, at least I'm
|
||||
housebroken" release, is now available for
|
||||
FreeBSD. This release is jammed packed with
|
||||
goodies including Evolution 1.5, gnome-network,
|
||||
|
|
@ -96,7 +96,7 @@
|
|||
released. However, it can be obtained from the
|
||||
<a href="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi">MarcusCom CVS repository</a>
|
||||
with the help of the ``marcusmerge'' script. For
|
||||
a complete list of what's changed, checkout the
|
||||
a complete list of what's changed, checkout the
|
||||
<a href="http://mail.gnome.org/archives/gnome-announce-list/2003-November/msg00095.html">release announcement</a>.</p>
|
||||
</event>
|
||||
|
||||
|
|
@ -110,7 +110,7 @@
|
|||
<a href="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi">MarcusCom CVS repository</a>.
|
||||
Be sure to get the latest copy of the ``marcusmerge''
|
||||
script while you're there to help with the upgrade.
|
||||
Thanks to a few of our users, there is also a
|
||||
Thanks to a few of our users, there is also a
|
||||
<a href="http://www.marcuscom.com/marcusmerge.8.html">man page</a>
|
||||
to go with this script. NOTE: this is a
|
||||
developers release, and bugs will exist. If you're
|
||||
|
|
@ -137,7 +137,7 @@
|
|||
</day>
|
||||
|
||||
</month>
|
||||
|
||||
|
||||
<month>
|
||||
<name>October</name>
|
||||
|
||||
|
|
@ -149,9 +149,9 @@
|
|||
|
||||
<p>Thanks to work by <a href="mailto:marcel@FreeBSD.org">
|
||||
Marcel Moolenaar</a>, the GNOME desktop now builds
|
||||
on ia64. There are runtime issues to be resolved,
|
||||
on ia64. There are runtime issues to be resolved,
|
||||
but this was expected. Most importantly, we have new
|
||||
ways to exercise FreeBSD/ia64 in general and KSE/ia64
|
||||
ways to exercise FreeBSD/ia64 in general and KSE/ia64
|
||||
in particular. Not to mention that we can proceed
|
||||
porting and building other GNOME ports. GNOME for
|
||||
FreeBSD now runs on i386, Alpha, Sparc64, and ia64.
|
||||
|
|
@ -205,9 +205,9 @@
|
|||
<title>GNOME 2.4 Release Candidate 1 available for FreeBSD</title>
|
||||
|
||||
<p>The GNOME 2.4 Release Candidate 1 (aka "Kublai") desktop
|
||||
has been released and ported to FreeBSD. Those
|
||||
has been released and ported to FreeBSD. Those
|
||||
wanting to make GNOME 2.4 the best release ever
|
||||
should checkout the ``ports'' module per the
|
||||
should checkout the ``ports'' module per the
|
||||
instructions at the
|
||||
<a href="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi">MarcusCom CVS repository</a>.
|
||||
Be sure to get the ``marcusmerge'' script as well to
|
||||
|
|
@ -246,9 +246,9 @@
|
|||
|
||||
<event>
|
||||
<title>GNOME 2.4 Beta 1 desktop available for FreeBSD</title>
|
||||
<p>The GNOME 2.4 Beta 1 (aka "Jelme") desktop has been
|
||||
released, and ported to FreeBSD. For those of you
|
||||
chomping at the bit to test drive this baby, checkout
|
||||
<p>The GNOME 2.4 Beta 1 (aka "Jelme") desktop has been
|
||||
released, and ported to FreeBSD. For those of you
|
||||
chomping at the bit to test drive this baby, checkout
|
||||
the ``ports'' module per the instructions at the
|
||||
<a href="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi">MarcusCom CVS repository</a>.
|
||||
Be sure to get the ``marcusmerge'' script as well to
|
||||
|
|
@ -272,7 +272,7 @@
|
|||
<p><a href="mailto:bland@FreeBSD.org">Alexander
|
||||
Nedotsukov</a> has been granted a commit
|
||||
bit, and has joined the FreeBSD GNOME team.
|
||||
Alexander will be working on general GNOME
|
||||
Alexander will be working on general GNOME
|
||||
desktop porting and bug-busting as well as focusing
|
||||
on his ports of the GNOME 2 C++ bindings. Please
|
||||
join us in welcoming Alexander to the team!</p>
|
||||
|
|
@ -397,11 +397,11 @@
|
|||
<event>
|
||||
<title>GNOME 2.3.0 desktop available for FreeBSD</title>
|
||||
|
||||
<p>Calling all testers! The first of the GNOME 2.3
|
||||
<p>Calling all testers! The first of the GNOME 2.3
|
||||
development releases is now available. Code named
|
||||
"Mighty Atom," this release includes quite a few
|
||||
new proposed modules. The GNOME 2.3 snapshots will
|
||||
become the GNOME 2.4 desktop on or around
|
||||
become the GNOME 2.4 desktop on or around
|
||||
September 8. The full scoop can be found
|
||||
<a href="http://www.gnomedesktop.org/article.php?sid=1045">
|
||||
here</a>. Those wanting to test this release
|
||||
|
|
@ -469,9 +469,9 @@
|
|||
and ports have been made for FreeBSD. This is the
|
||||
last release candidate before GNOME 2.2 is released
|
||||
on February 5. For those wanting to test this
|
||||
release, checkout the ``ports'' module per the
|
||||
release, checkout the ``ports'' module per the
|
||||
instructions at
|
||||
<a href="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi">http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi</a>. A script is
|
||||
<a href="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi">http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi</a>. A script is
|
||||
also provided at that site to help in merging this
|
||||
tree with the official FreeBSD ports tree.</p>
|
||||
</event>
|
||||
|
|
@ -497,7 +497,7 @@
|
|||
<event>
|
||||
<title>GNOME desktop 2.2 Release Candidate 1 available for FreeBSD</title>
|
||||
|
||||
<p>The GNOME 2.1.90 desktop, "1.21 Jigawatts" release, is
|
||||
<p>The GNOME 2.1.90 desktop, "1.21 Jigawatts" release, is
|
||||
available, and ports have been made. This is the
|
||||
first release candidate for GNOME 2.2, and is
|
||||
considered to be quite stable. People wanting to
|
||||
|
|
@ -541,7 +541,7 @@
|
|||
For those wanting to particpate in the testing,
|
||||
the ports are available via anonymous CVS from
|
||||
MarcusCom. Checkout the ``ports'' module per the
|
||||
instructions at
|
||||
instructions at
|
||||
<a href="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi">http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi</a>.
|
||||
</p>
|
||||
</event>
|
||||
|
|
@ -549,17 +549,17 @@
|
|||
|
||||
<day>
|
||||
<name>1</name>
|
||||
|
||||
|
||||
<event>
|
||||
<title>GNOME 2.1.3 desktop available for FreeBSD</title>
|
||||
|
||||
<p>The GNOME 2.1.3 desktop, "Twin Pines" release, is
|
||||
available and ports have been made for it (including
|
||||
the GStreamer components!). For those wanting to
|
||||
test this next installment in the 2.1 developer
|
||||
test this next installment in the 2.1 developer
|
||||
series, ports are available via anonymous CVS from
|
||||
MarcusCom. Checkout the ``ports'' module per the
|
||||
instructions at
|
||||
instructions at
|
||||
<a href="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi">http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi</a>.
|
||||
</p>
|
||||
</event>
|
||||
|
|
@ -602,8 +602,8 @@
|
|||
newer modules (such as system-tray) haven't yet been
|
||||
ported. For those wanting to test this latest development
|
||||
snapshot, ports are available via anonymous CVS from
|
||||
MarcusCom. Checkout the ``ports'' module per the
|
||||
instructions at
|
||||
MarcusCom. Checkout the ``ports'' module per the
|
||||
instructions at
|
||||
<a href="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi">
|
||||
http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi</a>.
|
||||
</p>
|
||||
|
|
@ -639,7 +639,7 @@
|
|||
|
||||
<p>The GNOME 2.1.0 desktop, "88MPH" release is available, and ports
|
||||
have been made for those wanting to test. The ports are available
|
||||
via CVS from MarcsuCom. A cvsweb interface is available from
|
||||
via CVS from MarcsuCom. A cvsweb interface is available from
|
||||
<a href="http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi">
|
||||
http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi</a>. The module
|
||||
name is ``ports''. Instructions for checking out the
|
||||
|
|
@ -696,7 +696,7 @@
|
|||
at <a href="http://www.gnome.org/start/2.0/">
|
||||
http://www.gnome.org/start/2.0/</a>. The ports collection is
|
||||
already in sync with 2.0.1, and 2.0.1 packages are available for
|
||||
i386 -stable from
|
||||
i386 -stable from
|
||||
<a href="http://www.marcuscom.com/downloads/packages/gnome/">
|
||||
http://www.marcuscom.com/downloads/packages/gnome/</a>.
|
||||
</p>
|
||||
|
|
@ -709,7 +709,7 @@
|
|||
<event>
|
||||
<title>GNOME 2 Packages Now Available!</title>
|
||||
|
||||
<p>GNOME 2 packages for i386 FreeBSD-stable have been posted to
|
||||
<p>GNOME 2 packages for i386 FreeBSD-stable have been posted to
|
||||
<a href="http://www.marcuscom.com/downloads/packages/gnome/">
|
||||
http://www.marcuscom.com/downloads/packages/gnome/</a>. Both
|
||||
.tgz and .tbz packages have been posted. This includes everything
|
||||
|
|
@ -746,7 +746,7 @@
|
|||
|
||||
<p>The FreeBSD GNOME team is proud to announce that GNOME 2.0
|
||||
Release has been ported to FreeBSD. This comes four days after
|
||||
the GNOME Project made their press release. Look for
|
||||
the GNOME Project made their press release. Look for
|
||||
documentation updates to cover the new GNOME 2.0 desktop.</p>
|
||||
</event>
|
||||
</day>
|
||||
|
|
@ -809,7 +809,7 @@
|
|||
Another goal is to provide set of pre-built GNOME2 binary
|
||||
packages on the official FreeBSD 4.6 release media along with
|
||||
GNOME 1.4 bits and pieces.</p>
|
||||
|
||||
|
||||
<p>We would encourage any help from our users in the form of
|
||||
problem reports, patches, suggestions etc.</p>
|
||||
</event>
|
||||
|
|
@ -873,7 +873,7 @@
|
|||
and FreeBSD port was updated accordingly. Update is strongly
|
||||
recommended to all current users.</p>
|
||||
</event>
|
||||
</day>
|
||||
</day>
|
||||
|
||||
<day>
|
||||
<name>11</name>
|
||||
|
|
@ -942,7 +942,7 @@
|
|||
</event>
|
||||
|
||||
</day>
|
||||
|
||||
|
||||
|
||||
<day>
|
||||
<name>28</name>
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
<?xml version="1.0" encoding="ISO-8859-1" ?>
|
||||
|
||||
<!-- $FreeBSD: www/en/gnome/newsflash.xsl,v 1.2 2002/01/28 16:38:30 sobomax Exp $ -->
|
||||
<!-- $FreeBSD: www/en/gnome/newsflash.xsl,v 1.3 2003/08/26 07:44:05 marcus Exp $ -->
|
||||
|
||||
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"
|
||||
xmlns:cvs="http://www.FreeBSD.org/XML/CVS" exclude-result-prefixes="cvs">
|
||||
|
|
@ -14,12 +14,12 @@
|
|||
<xsl:variable name="date">
|
||||
<xsl:value-of select="//cvs:keyword[@name='freebsd']"/>
|
||||
</xsl:variable>
|
||||
|
||||
|
||||
<xsl:output type="html" encoding="iso-8859-1"/>
|
||||
|
||||
<xsl:template match="news">
|
||||
<html>
|
||||
|
||||
|
||||
<xsl:copy-of select="$header1"/>
|
||||
|
||||
<body bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#840084"
|
||||
|
|
@ -32,17 +32,17 @@
|
|||
inside an attribute is "{$variable}".
|
||||
|
||||
This is just dis-similar enough to Perl and the shell that you
|
||||
end up writing ${variable} all the time, and then scratch your
|
||||
end up writing ${variable} all the time, and then scratch your
|
||||
head wondering why the stylesheet isn't working.-->
|
||||
|
||||
<!-- Also notice that because this is now XML and not SGML, empty
|
||||
elements, like IMG, must have a trailing "/" just inside the
|
||||
elements, like IMG, must have a trailing "/" just inside the
|
||||
closing angle bracket, like this " ... />" -->
|
||||
<img src="{$base}/gifs/news.jpg" align="right" border="0" width="193"
|
||||
height="144" alt="FreeBSD GNOME News"/>
|
||||
|
||||
<xsl:apply-templates select="descendant::month"/>
|
||||
|
||||
|
||||
<xsl:copy-of select="$newshome"/>
|
||||
<xsl:copy-of select="$footer"/>
|
||||
</body>
|
||||
|
|
@ -50,7 +50,7 @@
|
|||
</xsl:template>
|
||||
|
||||
<!-- Everything that follows are templates for the rest of the content -->
|
||||
|
||||
|
||||
<xsl:template match="month">
|
||||
<h1><xsl:value-of select="name"/>
|
||||
<xsl:text> </xsl:text>
|
||||
|
|
@ -74,7 +74,7 @@
|
|||
|
||||
<b><xsl:value-of select="ancestor::day/name"/>
|
||||
<xsl:text> </xsl:text>
|
||||
<xsl:value-of select="ancestor::month/name"/>,
|
||||
<xsl:value-of select="ancestor::month/name"/>,
|
||||
<xsl:value-of select="ancestor::year/name"/>:</b><xsl:text> </xsl:text>
|
||||
<xsl:apply-templates select="p"/>
|
||||
</p>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $FreeBSD: www/en/gnome/rss.xsl,v 1.1 2002/11/21 21:39:42 marcus Exp $ -->
|
||||
<!-- $FreeBSD: www/en/gnome/rss.xsl,v 1.2 2002/11/24 08:43:31 marcus Exp $ -->
|
||||
|
||||
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
|
||||
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
|
||||
|
|
@ -9,7 +9,7 @@
|
|||
<xsl:import href="includes.xsl"/>
|
||||
|
||||
<xsl:variable name="base" select="'..'"/>
|
||||
<xsl:variable name="date" select="'$FreeBSD$'"/>
|
||||
<xsl:variable name="date" select="'$FreeBSD: www/en/gnome/rss.xsl,v 1.2 2002/11/24 08:43:31 marcus Exp $'"/>
|
||||
<xsl:variable name="title" select="'FreeBSD GNOME Project News System'"/>
|
||||
|
||||
<xsl:output type="xml" />
|
||||
|
|
@ -18,7 +18,7 @@
|
|||
<rdf:RDF
|
||||
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
|
||||
xmlns="http://my.netscape.com/rdf/simple/0.9/">
|
||||
|
||||
|
||||
<channel>
|
||||
<title>FreeBSD GNOME Project News</title>
|
||||
<link>http://www.FreeBSD.org/gnome</link>
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
|
||||
<!ENTITY base CDATA "..">
|
||||
<!ENTITY date "$FreeBSD: www/en/gnome/screenshots.sgml,v 1.26 2003/12/28 02:11:43 adamw Exp $">
|
||||
<!ENTITY date "$FreeBSD: www/en/gnome/screenshots.sgml,v 1.27 2004/01/08 01:43:35 adamw Exp $">
|
||||
<!ENTITY title "FreeBSD GNOME Project: Screenshots">
|
||||
<!ENTITY % gnomeincludes SYSTEM "includes.sgml"> %gnomeincludes;
|
||||
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
|
||||
|
|
@ -14,7 +14,7 @@
|
|||
<h3>GNOME 2.4 Screenshots</h3>
|
||||
|
||||
<p><b>Dual screens at 2048x768 showing off the
|
||||
Epiphany web browser, and the new Themus and
|
||||
Epiphany web browser, and the new Themus and
|
||||
CD-Burner Nautilus views:</b><br>
|
||||
<a href="images/ss11.png"><img src="images/ss11-tn.png" border="0" alt="Screen Shot 11" title="Screen Shot 11">
|
||||
</a>
|
||||
|
|
@ -26,7 +26,7 @@
|
|||
</a>
|
||||
</p>
|
||||
|
||||
<p><b>Xchat, Xmms, StickyNotes, and GKrellM with the Koynacity-Blue
|
||||
<p><b>Xchat, Xmms, StickyNotes, and GKrellM with the Koynacity-Blue
|
||||
metacity, Aquativo 1.5 GTK, and Flat blue icon themes:</b><br>
|
||||
<a href="images/ss13.png"><img src="images/ss13-tn.png" border="0" alt="Screen Shot 13" title="Screen Shot 13">
|
||||
</a>
|
||||
|
|
|
|||
Loading…
Reference in a new issue