[postgis-devel] README reduction (1.1.0 closeup call)

[Paul Ramsey]

The principle is not low technology, but low friction for first  
installers.  All the minimal information you need at your fingertips  
to quickly go from no-PostGIS to running-PostGIS.  So the verbose  
manual will never be a substitute for a terse guide in the README.

P

On 14-Dec-05, at 9:15 AM, strk at refractions.net wrote:

> On Wed, Dec 14, 2005 at 06:07:25PM +0100, strk at refractions.net wrote:
>> On Wed, Dec 14, 2005 at 08:45:01AM -0800, Paul Ramsey wrote:
>>> Sorry, no dice.  A pet peave of mine is having to leave my
>>> commandline for installation instructions when getting new software.
>>> INSTALLATION and UPGRADING are required, and USAGE is a nice-to- 
>>> have,
>>> in terms of giving very basic instructions sufficient to see that  
>>> the
>>> software works as advertised.
>>
>> I don't have to leave commandline for browsing postgis manual,
>> anyway point taken (respect for low technology).
>>
>> How about using xsltproc (or lynx -dump) to generate a
>> postgis-manual.txt ?
>
> mmm. I tried both, and both output suck :/
> Let's get back to hand-written version.
>
> --strk;
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel