severity 703249 wishlist
tags 703249 + wontfix
thanks

On 17.03.2013 17:39, Konrad Vrba wrote:
> Problem: I would like to kindly suggest, that rsyslog-mysql should not
> depend on dbconfig-common (it can be recommended, but not required)
> 
> Reason: rsyslog-mysql is used to log into mysql database, which in
> most cases is on a remote machine (one server, many clients).
> dbconfig-common tries to set up mysql database automatically, but on a
> local client.  I have two objections to this:
> 1) dbconfig-common does not do any useful work (the database already
> exists on the server), and therefore should not be required to be
> installed. It only confuses things.
> 2) being interactive,  dbconfig-common breaks automated upgrade
> scripts (DEBIAN_FRONTEND=noninteractive apt-get -q -y upgrade), by
> waiting for user input
> 
> Summary: I believe, packages should not be installed thoughtlessly.
> Only packages that are really needed should be installed, as more
> packages means more possible (security) bugs and dependency problems.
> Additionally in case of dbconfig-common, this is a huge package (I
> have counted 249 files !!!) which cannot be removed even after its
> (supposed) job has been done. I feel strongly that debian users should
> have as much freedom as possible to choose which packages they wish to
> install.

I don't find your arguments convincing. dbconfig-common is *not* a huge
package, it's just about 1MB of installed size without further dependencies.
Second, dbconfig-common can be used to configure rsyslog for remote
mysql servers.
Third, I don't think a remote mysql servier is the common case.
Fourth, you can skip dbconfig-common altogether if you don't like it and
setup rsyslog-mysql manually.

Thus marking the bug as wishlist and wontfix as with the arguments
provided so far I don't see a reason to change it.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to