[postgis-devel] Documentation and comments in tarball

Paul Ramsey pramsey at opengeo.org
Mon Jan 9 08:47:56 PST 2012


I tend to want to see HTML shipped. PDF not really. Comments SQL I
think should be shipped. On chunk HTML vs one page, I have no idea.
One page is easier to search :)

P.

On Mon, Jan 9, 2012 at 6:32 AM, Sandro Santilli <strk at keybit.net> wrote:
> Following up http://trac.osgeo.org/postgis/ticket/626
> to avoid discussion on trac, I'd like to hear your opinion
> about distributing documentation and sql comments in tarballs.
>
> A quick look at http://www.postgis.org/download/ shows:
>
>  1.4.2 shipped with with single-page HTML manual (incl. generated images)
>
>  1.5.3 shipped with with single-page HTML manual (incl. generated images)
>  and the postgis_comments.sql file.
>
>  2.0.0svn shipped with chunked HTML manual (incl. generated images) and
>  the PDF manual.
>
> Is there a general consensus about what should be shipped and what not
> in the tarball ? My personal opinion is that only sources should be in
> a source tarball, and documentation is no exception, but if the majority
> decides for a different setup please let me know and I'll update the
> make_dist.sh script accordingly.
>
> Thank you.
>
> --strk;
>
>  ()   Free GIS & Flash consultant/developer
>  /\   http://strk.keybit.net/services.html
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel



More information about the postgis-devel mailing list