[postgis-devel] Documentation and comments in tarball

Sandro Santilli strk at keybit.net
Tue Jan 10 00:01:00 PST 2012


On Tue, Jan 10, 2012 at 08:53:47AM +0100, Sandro Santilli wrote:
> On Mon, Jan 09, 2012 at 03:55:58PM -0500, Paragon Corporation wrote:
> > 
> > 
> > >  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.
> > 
> > > As a packager, I would like to see things included if not including them
> > would greatly expand the required build dependencies, where 'greatly' in
> > practice is about not dragging in huge xml toolchains that otherwise would
> > not be needed.  And otherwise, I have a bias against including generatable
> > files.
> 
> The thing is: if you just want to _read_ the documentation, get a binary 
> package for them. If you want to contribute then you'll need the additional
> dependencies anyway.
> 
> Comments add 480 Kb, requires: xsltproc
> single-page html adds 2 Mb + 1.24 Mb for images, requires: xsltproc, imagemagick
> pdf adds 7.83 Mb, requires: dblatex, imagemagick
> 
> Both HTML and PDF documentation could be made available online.

To complete the picture: 1.5.3 tarball was 3.6 Mb, did _not_ contain PDF,
contained a single-page HTML (1.12 Mb) and only 89 images while current
trunk has 152. Only 43 images are not generated in trunk.

--strk; 

  ()   Free GIS & Flash consultant/developer
  /\   http://strk.keybit.net/services.html



More information about the postgis-devel mailing list