Re: Packages should not Conflict on the basis of duplicate functionality
> Of course. Now if you built them yourself, dpkg wouldn't touch them.
If I wanted to build them myself, I would use Slackware.
If I repackage them I will need to remove the Conflicts line from
the control files every single time I upgrade.
> People who want such "complex" setups should have enough sense to be able to
> figure out how to make them work, without imposing additional difficulty on
> the maintainers for such a rare case. There is not generally a use for more
> than one POP server, ident server, mail server, etc. I can find exceptions,
> but it isn't Debian's job to make every possible configuration easy, just
> the most likely and typical ones.
The most likely and typical configurations are those for a home workstation.
So let's screw anyone who wants to use Debian on a production server.
I run apache and roxen on the same machine. That's hardly typical.
Why on earth would anyone want to run two different web servers?
These two packages should obviously conflict since they're both
web servers and want to grab port 80.
They both provide httpd; should I file bugs against them demanding that
they conflict with it too?
Reply to: