On Thu, Oct 20, 2005 at 12:40 +0200, Frank Küster wrote:
> mfw was the name of the mf binary with X11 support, mf-nowin is the name
> without. In 2.0, /usr/bin/mf was a symlink to /usr/bin/mfw, now it the
> binary itself is called /usr/bin/mf.
>
> I think this is an upstream change,
Yes, this is an upstream change.
teTeX 2.0.2 compilde from source has
mf -> mfw
mf-nowin
mfw
teTeX 3.0 compiled from source has
mf
mf-nowin
> but restoring the old behavior
> probably won't hurt anybody. We could also create the reverse symlink
> (mfw -> mf), but then we get problems in case we want to split of a
> tetex-bin-nowin package and want /usr/bin/mf to be managed with
> update-alternatives.
On Thu, Oct 20, 2005 at 12:40 +0200, Frank Küster wrote:
> mfw was the name of the mf binary with X11 support, mf-nowin is the name
> without. In 2.0, /usr/bin/mf was a symlink to /usr/bin/mfw, now it the
> binary itself is called /usr/bin/mf.
>
> I think this is an upstream change,
Yes, this is an upstream change.
teTeX 2.0.2 compilde from source has
mf -> mfw
mf-nowin
mfw
teTeX 3.0 compiled from source has
mf
mf-nowin
> but restoring the old behavior alternatives.
> probably won't hurt anybody. We could also create the reverse symlink
> (mfw -> mf), but then we get problems in case we want to split of a
> tetex-bin-nowin package and want /usr/bin/mf to be managed with
> update-
ACK
cheerio
ralf