<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: [postgis-devel] Updated SVN documentation</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>> The "complete" install guide should probably be as Paul suggests.<BR>
<BR>
> I'm torn about including URLs to the proj and geos downloads, primarily<BR>
> because it then becomes a continual chore to update them ... it seems<BR>
> like the sort of thing that belongs in a howto on a wiki more than in<BR>
> the core documentation. The postgresql documentation provides only the<BR>
> very generic (and long lived) <A HREF="ftp://ftp.gnu.org/gnu/">ftp://ftp.gnu.org/gnu/</A> as a reference for<BR>
> those looking to download pre-requisite packages. To follow suit, we<BR>
> could simply link to <A HREF="http://download.osgeo.org/">http://download.osgeo.org/</A> which is about 90% of<BR>
> the way to linking to the latest packages, without requiring updates<BR>
> every time a new version comes out.<BR>
<BR>
And how often do these versions change relative to the frequency with which we change PostGIS? I would say about the same frequency. So we should be revisiting this section just as frequently.<BR>
Updating 2 dependencies in my mind is not a big chore.<BR>
<BR>
> My 2 cents as someone who has installed a lot of software on a lot of<BR>
> Linux (and other) boxen over the years.<BR>
<BR>
> Chris<BR>
<BR>
Exactly my point Chris - you and Mark have installed a lot of Linux software. We are not writing the<BR>
documentation for people like you. You already know how to install these things. I'm closer to<BR>
the audience we want to target - and I find trying to wade my way to another site to figure out<BR>
which version of stuff I have to install extremely frustrating.<BR>
<BR>
PostgreSQL is a much larger project with many more dependencies and dependencies they have less control over. It makes sense for them to just simply link to another set of instructions. It doesn't for PostGIS.<BR>
<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
The substance of this message, including any attachments, may be confidential, legally privileged and/or exempt from disclosure pursuant to Massachusetts law. It is intended solely for the addressee. If you received this in error, please contact the sender and delete the material from any computer.
</STRONG></P></BODY></HTML>
<P><hr size=1></P>
<P><STRONG><font size="2" color="339900"> Help make the earth a greener place. If at all possible resist printing this email and join us in saving paper. </p> <p> </font></STRONG></P>