# $ApsCVS: www/support.wml,v 1.24 2002/11/11 09:01:01 andreas Exp $
#use wml::tmpl::lbpage file=$(ROOT)/support.html
<page_title name="Support">

<linkgroup name="Apsfilter Support">
  <p><b>Communication concerning apsfilter please exclusively over 
  the mailing-lists !</b>
  <p>Please don't write mails to apsfilter author (Andreas Klemm) and
  developers directly. Sorry, but they will be ignored !
  <br>Use the proper mailinglist ! You will get faster responses, because
  more people will listen to you.
  <br>Additionally this increases other peoples chance to get help by
  searching or browsing the <mlarchive>.
  <p>
</linkgroup>

<linkgroup name="SuSE user please read this">
  <p>SuSE Linux contains a magic print filter that was based on
  apsfilter many years ago. This product is <b>completely different</b>
  to apsfilter.
  <p>Unfortunately SuSE company has still used the name apsfilter
  in their handbook, in different lpd and susefilter config files
  and in susefilters path names. The latter seems to be the reason
  why they change the name apsfilter to susefilter so reluctantly.
  <p>Well, SuSE users, if you didn't install apsfilter from source, then
  we can be 99.9% sure, that you are running susefilter. If you have any
  problems with susefilter, please ask SuSE support. Thanks.
</linkgroup>

<linkgroup name="Howto report bugs or problems with 'apsfilter-bug' script">
  <p>Please use the new utility "apsfilter-bug".
  <p>It automatically presents to you some standard questions in an
  editor window you should answer and automatically sends your
  problem report to the proper apsfilter mailinglist.
</linkgroup>

<linkgroup name="Mailinglists">
  <p>The following apsfilter mailinglists are available (the number of
  subscribed users in parenthesis):
  <li><mlapsannounce>
	(<:=mlsize("apsfilter-announce"):>)
	</li>
  <li><mlapschat>
	(<:=mlsize("apsfilter-chat"):>)
	</li>
  <li><mlapscurrent>
	(<:=mlsize("apsfilter-current"):>)
	</li>
  <li><mlapscvs>
	(<:=mlsize("apsfilter-cvs"):>)
	</li>
  <li><mlapsdevel>
	(<:=mlsize("apsfilter-devel"):>)
	, closed developer group
	</li>
  <li><mlapsdoc>
	(<:=mlsize("apsfilter-doc"):>)
	</li>
  <li><mlapshackers>
	(<:=mlsize("apsfilter-hackers"):>)
	</li>
  <li><mlapshelp>
	(<:=mlsize("apsfilter-help"):>)
	</li>
  <li><mlapshilfe>
	(<:=mlsize("apsfilter-hilfe"):>)
	, german support list
	</li>
  <li><mlapsprinting>
	(<:=mlsize("apsfilter-printing"):>)
	</li>
  <li><mlapsstable>
	(<:=mlsize("apsfilter-stable"):>)
	</li>
<p>
  To subscribe to an apsfilter mailing-list send mail to:
  <blockquote>
	<majordomo>
  </blockquote>
  with the following line in the body of the mail:
  <blockquote>
  	subscribe apsfilter-<i>listname</i>
  </blockquote>
</linkgroup>

<linkgroup name="Mailing List Archive">
  <p>A browseable and searchable <mlarchive> is available for help,
  online support documentation and simply for reference.
  <p>
</linkgroup>

<linkgroup name="CVS Repository Browser">
  <p>The <i>cvsweb</i> CGI script allows you to browse through the
  apsfilter CVS repository. There you can create diffs and browse
  through the commit logs:
  <blockquote>
	<a href="http://www.apsfilter.org/cgi-bin/cvsweb.cgi">http://www.apsfilter.org/cgi-bin/cvsweb.cgi</a>
  </blockquote>
</linkgroup>

<linkgroup name="Always 'up to date' with Anonymous CVS Server">
  <p>Another way to get the latest -STABLE or -developement
  version of apsfilter is to use the Concurrent Version System
  (CVS). You are allowed to checkout either version 
  from the apsfilter projects anonymous CVS server.
<p>Quick historical note: anonymous CVS support has been implemented
  by <freebsd> developement team.
<p>Here an example how to use it:
<code>  setenv CVSROOT :pserver:cvs@apsfilter.org:/var/apscvs/APSCVS 
  cvs login 
  cvs checkout -r RELEASE_TAG -P apsfilter</code>
<p>Use <i>"RELENG_7"</i> as RELEASE_TAG to get the latest stable
   release <br>use <i>"HEAD"</i> or simply nothing to checkout the
  latest developement version.
<p>As ordinary user you shouldn't use the developement version.
  Normal changes and bugfixes are always committed to the 
  -developement AND the -stable version.
  <p>
</linkgroup>

# vim: set ft=html: