Lamar Owen <lamar.owen@wgcr.org> writes:
> 1.) Addition of a postgresql-lib subpackage. Rationale: those using
> just the Perl, Python, or Tcl clients may not want the full psql cli and
> documetation installed just to use their client. This package would
> simply be the shared object dynamic load libraries necessary for any
> client.
Sounds like a good idea.
> 2.) Addition of a postgresql-pltcl subpackage. Rationale: pl/tcl is
> currently included as part of the postgresql-tcl package. If someone
> has the need for a tcl-client ONLY installation, they currently cannot
> do so due to the postgresql-tcl package's dependency upon the server
> subpackage being loaded. Likewise, answering the question 'why not put
> pl/tcl in the main server package', someone needing the server package,
> but not pl/tcl, bight not want to have the full Tcl client installed
> just to run a server.
The package is 64 k. Why split it?
> I am a minimalist not because of a desire to save disk space -- disk is
> cheap, after all. I am a minimalist because of security -- if I don't
> _need_ Perl installed, then I shouldn't be forced to install Perl, for
> instance.
I've yet to see a security hole from documentation :)
>
--
Trond Eivind Glomsrød
Red Hat, Inc.
