I don't really follow the argument here. The most convenient situation is of course when tetex-3 has already been installed when ec-fonts is, since then the installation script for ec-fonts can call updmap in the existing tetex. In fact, I would propose a dependency such that ec-fonts is always installed after tetex-*, also since the font itself doesn't make sense without tetex.
The problem is for users who have tetex-2 installed, then install ec-fonts (which runs updmap on tetex-2) and after that upgrade to tetex-3. An ugly workaround would be to make separate packages of ec-fonts for tetex-2 and tetex-3. They could have exactly the same contents, the point is just to be able to invoke the installation script of ec-fonts after the installation of tetex-3.
I still don't see any reason to involve anything related to ec-fonts in the installation scripts for LilyPond.
/Mats
Jan Nieuwenhuizen wrote:
Bertalan Fodor writes:
So, the new lilypond must contain the updmap also for ec-fonts-mftraced. This is a must, since ec-fonts doesn't rely on tetex, so tetex-3 may be installed before ec-fonts.
Hmm, ok.
Because tetex-3.0 will break existing lilypond, we must release tetex-3.0 for cygwin at the same time with lilypond-2.4.3 and ec-fonts-mftraced.
Yes. I've added removal of /var/lib/texmf to the post-texmf.sh script, so I can send an update notice right after you lilypond with tetex-3.0 fixes is installed in Cywgin.
Jan.
-- ============================================= Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe =============================================
_______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
