Re: Bug#577638: mpich2: conflict over the mpd binary
On 13/04/10 at 09:13 -0500, Pavan Balaji wrote:
> On 04/13/2010 08:42 AM, Lucas Nussbaum wrote:
> >What do you think we should do?
> I don't have a short-term solution for this, but in the 1.3 series,
> Hydra is the default process manager instead of mpd. So, by default,
> there will not be any mpd* installed (it'll still be available for
> people who want to configure with mpd using --with-pm=mpd). The
> timeline for releasing 1.3 is late summer unfortunately (1.3a1 is
> already out).
Dear release team,
Given that we have a way out of this for after squeeze (switching to
hydra as the PM, thus droppping the mpd binary), I'm very tempted to
ignore that problem for squeeze (and keep the current "solution" of
conflicting with mpd).
Renaming the mpd binary in the mpich2 package is likely to generate a
lot more many unsatisfied users than the conflict. It will result in a
lot of documentations being changed with "... except if you use Debian,
where they thought better and renamed mpd to mpich2-mpd".
Additionally, there's no easy way to do the renaming. It could possibly
introduce subtle breakages.
So, would you consider squeeze-ignor'ing this bug?
| Lucas Nussbaum
| email@example.com http://www.lucas-nussbaum.net/ |
| jabber: firstname.lastname@example.org GPG: 1024D/023B3F4F |