<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.0.4">
</HEAD>
<BODY>
Hi,<BR>
<BR>
in your list, you have a few things I didnt find in the Qim, and which I would like to know whether they are really needed now..:<BR>
----<BR>
<TT>for prog in make patch binutils gcc procmail zlib expat readline libiconv \<BR>
perl perl-ldap perl-openpkg perl-ds perl-time perl-xml perl-term perl-crypto \<BR>
perl-conv openssl perl-ssl perl-sys perl-util perl-mail perl-net \<BR>
perl-www m4 bison flex pcre fsl gdbm db mm ncurses sed imap gettext \<BR>
apache db imapd openldap postfix proftpd sasl; do<BR>
--------<BR>
<BR>
my question is about the libiconv and sed packages, they aren't listed on the Qim instructions, which I know aren't up to date, but still...</TT><BR>
(<A HREF="http://intevation.de/cgi-bin/viewcvs-kolab.cgi/server/doc/QIM?rev=HEAD&content-type=text/vnd.viewcvs-markup("><TT>http://intevation.de/cgi-bin/viewcvs-kolab.cgi/server/doc/QIM?rev=HEAD&content-type=text/vnd.viewcvs-markup</TT></A>)<BR>
<BR>
Maarten<BR>
<TT><BR>
</TT><BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE><FONT COLOR="#737373"><I>This gets the latest of our packages from OpenPKG current and saves
them in the current folder. The idea would be to have the "getting" decoupled
from the build script.
Next step is to get all the files from CVS (access varying depending if you
use anonymous or you have CVS developer access) and then have everything
together for a complete, ground-up build for Kolab CVS.
Have fun!</I></FONT></PRE>
</BLOCKQUOTE>
</BODY>
</HTML>