Comment 28 for bug 1225

2007/4/18, Murray Cumming <email address hidden>:
>
>
> The Postgresql binary is an implementation detail that should not be of
> interest to users. The problem here is not that Postgresql is installed,
> but that an unnecessary and unused instance of Postgresql is _started_
> when it is installed just for Glom.
>

Why would I want a program installed that i wouldn't want to run EVER?

May be for you it isn't very important to have a bunch of MB wasted in your
hard disk, but think for a moment in use cases different from yours. What
happens when you have a system fetching a disk image through network to boot
from that? Each extra MB is a waste of bandwidth and each new client adds
more waste.

Even when you have enough HD, it adds time and bandwidth usage in each
update for something you doesn't need at all.

You seem to take the point of view of an end user, but I take the view of an
admin/sysop and it's a problem for me to have postgresql installed in
systems I doesn't want it. But, hey! I'm only one of many! Maybe I'm
mistaken.

You can make what you want (installation of postgresql while installing
glom) in a way that makes it possible for other to install it without the
server (using the virtual packages and dependencies). Why are you so
reticent to allow people the choice? Is there anything I'm not aware of?