Sorry to bring up this old issue again, but I think we tried to solve a
non-issue or possibly solve some problem the wrong way.
It should never be necessary to run updmap for the ec-fonts since
the map file is specified explicitly in the call of dvips inside
lilypond and the documentation describes
Jan Nieuwenhuizen writes:
>> - release lilypond packaged for tetex-2.0
>> - release tetex-3
>> - release ec-fonts for tetex-3, with dependency on tetex
>> - release lilypond packaged for tetex-3.0
>
> Yes, this is cleaner than the lilypond updmap hack.
So are we good to go now?
Jan.
--
Jan Nieu
Bertalan Fodor writes:
> I have misunderstood something.
> So here what do you think the correct order will be for releasing the
> packages?
>
> - release lilypond packaged for tetex-2.0
> - release tetex-3
> - release ec-fonts for tetex-3, with dependency on tetex
> - release lilypond packaged fo
I have misunderstood something.
So here what do you think the correct order will be for releasing the
packages?
- release lilypond packaged for tetex-2.0
- release tetex-3
- release ec-fonts for tetex-3, with dependency on tetex
- release lilypond packaged for tetex-3.0
Bert
Jan Nieuwenhuizen írt
Bertalan Fodor writes:
>> 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'm not sure if it is possible.
Why not, just increase the -build version?
Jan.
--
Jan Nieuwenhuizen <[EM
Bertalan Fodor wrote:
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.
Some core maintainer of cygwin pointed us to not make font packages
dependent of tetex. However, we can put this depende
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.
Some core maintainer of cygwin pointed us to not make font packages
dependent of tetex. However, we can put this dependency back, because we
ha
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
ins
Bertalan Fodor writes:
>>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.
>>
>>
> You must also remove the tetex-2.0 generated files from /usr/share/web2c
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.
You must also remove the tetex-2.0 generated files from /usr/share/web2c
mf.base, *.fmt, *.emft
Bert
_
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 cygw
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.
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 a
Mats Bengtsson writes:
>> How about adding this to lilypond?
>
> No, that's something for the installation script of ec-fonts-mftraced,
Yes, you're right.
> but as Bertalan pointed out, if might fail if someone updates from
> tetex-2 to tetex-3.
But we must try our very best not to let this fai
Jan Nieuwenhuizen wrote:
Bertalan Fodor writes:
I made the tests:
1. purge c:\cygwin
2. install old lilypond-2.4.2-1 with default settings - OK (this is
the test that that makes many user problem inexplicable)
:-)
3. install lilypond-2.4.3-1 (built against tetex-2.0) - OK
4. install tetex-3.0
FAIL2
ec-fonts are not found
Solution:
updmap --enable
Map=/usr/share/texmf/dvips/ec-fonts-mftraced/ec-mftrace.map
I'm not sure how to overcome this in the packages
How about adding this to lilypond?
Ok. I looked at /sauter-fonts-mftraced/GNUmakefile
I see:
# FIXME
Bertalan Fodor writes:
> I made the tests:
>
> 1. purge c:\cygwin
> 2. install old lilypond-2.4.2-1 with default settings - OK (this is
>the test that that makes many user problem inexplicable)
:-)
> 3. install lilypond-2.4.3-1 (built against tetex-2.0) - OK
> 4. install tetex-3.0.0-1
> FAIL
I made the tests:
1. purge c:\cygwin
2. install old lilypond-2.4.2-1 with default settings - OK (this is the
test that that makes many user problem inexplicable)
3. install lilypond-2.4.3-1 (built against tetex-2.0) - OK
4. install tetex-3.0.0-1
FAIL1
Invoking `latex \\nonstopmode \\input 1.te
Bertalan Fodor writes:
> Lilypond's been built with all tetex-3.0 fixes against tetex-2.0
Great.
> Now, what's next? According to your plan:
>
> 1. upload lilypond with all tetex-3.0 fixes, built against tetex-2.0
> 2. upload tetex
> 3. upload lilypond, built against tetex-3.0
>
> Now 1. c
Ok. Fine. Tetex install-uninstall is somewhat problematic, I had to
purge the texmf tree again. And reinstall tex twice :-)
Lilypond's been built with all tetex-3.0 fixes against tetex-2.0
Now, what's next? According to your plan:
1. upload lilypond with all tetex-3.0 fixes, built against tetex-
For more thorough debugging of why kpathsea doesn't find a particular
file or directory, you can set the environment variable KPATHSEA_DEBUG,
see http://www.fptex.org/kpathsea/kpathsea_2.html
/Mats
Jan Nieuwenhuizen wrote:
Bertalan Fodor writes:
Trying to build 2.4CVS with tetex-2.0
Almost eve
Bertalan Fodor writes:
> Trying to build 2.4CVS with tetex-2.0
>
> Almost everything works, but feta outline fonts are not found:
This is quite strange, as all tetex-3.0/2.0 changes should have
been compatibility features.
Can you try the usual path of finding out why this fails
* check TEXMF
Trying to build 2.4CVS with tetex-2.0
Almost everything works, but feta outline fonts are not found:
Invoking `dvips -Ppdf -u+ec-mftrace.map -u+lilypond.map -E -o
lily-1009715145.ep
s lily-1009715145'This is dvips(k) 5.92b Copyright 2002 Radical Eye
Software (ww
w.radicaleye.com)
' TeX output 200
Bertalan Fodor writes:
> I needed the following files at least to generate ecrm1000:
Yes, I see. All added to -tiny.
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
I needed the following files at least to generate ecrm1000:
ecrm.mf
exaccess.mf
exbase.mf
expseudo.mf
exroman.mf
However, it still put up some error, looking for ecruwest.mf
To eliminate errors I also had to install all fonts inputted in exroman.mf:
exaccent.mf
exbraces.mf
expunct.mf
exrdigit.mf
ex
Bertalan Fodor writes:
> I've done a test. Lilypond seems working with tetex-tiny, but there is
> still that ecrm1000 issue. I don't remember clearly what is the status
> of this problem .Will you include ecrm1000 in tetex-tiny?
No, ecrm1000 is generated. I did include ecrm.mf, but ecrm1000
incl
Hello,
I've done a test. Lilypond seems working with tetex-tiny, but there is
still that ecrm1000 issue. I don't remember clearly what is the status
of this problem .Will you include ecrm1000 in tetex-tiny?
Tomorrow I will try build 2.4CVS against tetex-2.0
Bert
kpathsea: Running mktextfm ecrm10
26 matches
Mail list logo
