Re: New on sourceware: texmf-20000804-2

2002-01-30 Thread Jan Nieuwenhuizen
[EMAIL PROTECTED] writes: > Well, I *did* skip the libpng update... Ok. Mabye people 'should be warned' about skipping updates, in some broadest sense of the word? > The only obvious indication that something is missing is > that the end of the post-install script, a window pops up > saying "m

Re: New on sourceware: texmf-20000804-2

2002-01-30 Thread Robert Collins
=== - Original Message - From: <[EMAIL PROTECTED]> > xv which I uses quite often, and it obviously depends > on libpng and I would rather not break it. The package maintainers try very hard to prevent *backwards* compatability issues. You should not need to fear upgrading. Rob -- Uns

RE: New on sourceware: texmf-20000804-2

2002-01-30 Thread hin-tak . leung
ething is missing is that the end of the post-install script, a window pops up saying "missing import ... ". -Original Message- From: Robert Collins [mailto:[EMAIL PROTECTED]] Sent: 30 January 2002 09:30 To: hin-tak.leung; Jan Nieuwenhuizen Cc: cygwin Subject: Re:

Re: New on sourceware: texmf-20000804-2

2002-01-30 Thread Robert Collins
- Original Message - From: "Jan Nieuwenhuizen" <[EMAIL PROTECTED]> > > BTW - pdftex in tetex-20001208-4 depends on the > > new (10-days-old) libpng 1.0.2. > > Hmm, that's not good. Does that package have a new name? Otherwise > we're in dire need of versioned depends. I wouldn't describ

Re: New on sourceware: texmf-20000804-2

2002-01-30 Thread Jan Nieuwenhuizen
[EMAIL PROTECTED] writes: > Just to confirm that with the latest tetex-20001208-4 > and the cygwin texmf-*-* packages I don't need to > set TEXMFMAIN anymore - although I still have > TEXINPUTS and the font related variables set to > "${HOME}/somewhere//:" for my CJK stuff. > > Well-done! Thank

Re: New on sourceware: texmf-20000804-2

2002-01-29 Thread Charles Wilson
lto:[EMAIL PROTECTED]] > Sent: 29 January 2002 13:46 > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: New on sourceware: texmf-2804-2 > > > [EMAIL PROTECTED] writes: > > >>My Texmf tree came from the stock teTeX 1.0.2 >> > > Ok, so y

RE: New on sourceware: texmf-20000804-2

2002-01-29 Thread hin-tak . leung
nhuizen [mailto:[EMAIL PROTECTED]] Sent: 29 January 2002 13:46 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: New on sourceware: texmf-2804-2 [EMAIL PROTECTED] writes: > My Texmf tree came from the stock teTeX 1.0.2 Ok, so you're not using the texmf packages, and not usin

Re: New on sourceware: texmf-20000804-2

2002-01-29 Thread Jan Nieuwenhuizen
[EMAIL PROTECTED] writes: > My Texmf tree came from the stock teTeX 1.0.2 Ok, so you're not using the texmf packages, and not using the latest tetex-beta... > Without setting TEXMFMAIN, it looks like latex is trying to look for > the texmf tree under //share rather than /usr/share . Could be.

RE: New on sourceware: texmf-20000804-2

2002-01-29 Thread hin-tak . leung
and I can see why the cygwin binaries shouldn't be able to do it correctly... -Original Message- From: Jan Nieuwenhuizen [mailto:[EMAIL PROTECTED]] Sent: 29 January 2002 10:29 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: New on sourceware: texmf-2804-2 [EMAIL PR

Re: New on sourceware: texmf-20000804-2

2002-01-29 Thread Jan Nieuwenhuizen
[EMAIL PROTECTED] writes: > I have been using 20001218-1 for quite a while now ... but I have > always had problems with having to set some environment variables. Did you install any of the texmf-tiny or texmf-base packages? > It is currently fully functional including typesetting CJK > docume

RE: New on sourceware: texmf-20000804-2

2002-01-29 Thread hin-tak . leung
Hiya, I have been using 20001218-1 for quite a while now (and in fact I did my own cygwin port of teTeX about 6 months before it was included in cygwin/contrib), but I have always had problems with having to set some environment variables. Currently for 20001218-1 I have to set TEXMFMAIN to /usr/