----- Original Message -----
From: "Peter Flynn" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Sunday, September 11, 2005 12:13 PM
Subject: OT: tetex RPMs (was: Re: Problems installing 1.3.6-1 RPMs
Jose' Matos wrote:
On Saturday 10 September 2005 19:23, Peter Flynn wrote:
2. yum install lyx.
Aaaarrrrggghhh! *Never*, never, never do this if you already have TeX.
Especially not if you have already carefully removed the outdated mess
that is the RH kludge of tetex, and replaced it with the real tetex from
the TeX Collection DVD.
If you do that you are on your own.
No, RH is on its own. Posters to c.t.t have consistently told users
of the RH tetex RPMs to trash them and replace them with the TUG CDs.
One other possibility is to redo the tetex rpm and then yum will work.
The TeX community has been trying for years to get whoever is
responsible for the RH tetex RPMs to update them properly. But they
insist on meddling with the directories and the subset of features
apparently deliberately to make it inconsistent with the TUG CDs. I
have no idea why they insist on doing this.
I read this description from an authoritative source (tug.org) and your
opinion is quite incoherent and inexperienced when compared to it.
The TeX Collection is self-described as having progressed to the point
"that comprehensive began to become incomprehensible". That is a
polite way of saying it had become a mess. It is no wonder that tetex
would have received a lower priority. You also single out RedHat.
Which of the many distros that using rpms or .deb have decided
they have the time to incorporate the endless stream of upgrades in
a system that in its entirety encompasses 6gigs?
Now in 2004, quite a few fundamental changes are made. And
2004 was released as a less perfected product than 2003. I don't
mean that the fundamental changes were a mistake or that a lot
of rough edges can be avoided in such a transition. But certainly
you are not going to find a bunch of Linux distros jumping onto
the bandwagon. They are not going to devote a large portion of
their release to TeX, nor many man-hours to fixing Tex. The idea
that the distros should do this, is undereducated and inexperienced.
You speak of having users and dispensing TeX advice for 20 years.
Peter wrote:
"Excellent! Never used yum before, so here goes. I wonder will
it work over the top of the mess that the RPMs left behind them...
But what is the .lyx directory you mentioned? Something that pre-
existed from an earlier installation? Or something you downloaded?"
SH: You've certainly done a good job in establishing your unique
qualifications for your sweeping pronouncements.
--------------------------------------------------------------------------:
http://www.tug.org/TUGboat/Articles/tb25-1/hagen-tl.pdf
"Beginning with version 8 TEX Live has become
the TEX Collection. It combines an out-of-the-box
TEX system and the complete CTAN repository
(Comprehensive TEX Archive Network: a snapshot
of almost all that is available for TEX users). TEX
systems started on floppy disks but soon filled CDROM's
and now DVD's. An archive of a couple of hundred files
grew into tens of thousands.
tree directories files bytes
texmf 3,750 45,000 626 M
texmf-extra 115 1,500 66 M
bin 16 2,500 250 M
source 380 6,900 104 M
If the CTAN archive is included we have a grand total
of 138,000 (unzipped even 420,000) files, organized
in 10,000 directories, totaling 5,906,870,829 bytes,
or about 6 GB.
With version 8 the organizers realized that
comprehensive began to become incomprehensible.
Even though the TDS, the TEX Directory Structure,
had brought some order in grouping files they
were still faced with the fact that old TEX systems
had been replaced with new systems in a continuous
process to adapt to changing operating systems,
improved text editors and more sophisticated and
generally available viewers and printers. Fundamental
changes appeared necessary and are implemented in
the TEX Collection 2004. This paper will focus on
some of the most important of these changes.
Summary:
When TEX Live 2004 shows up in your postbox,
update and things will work as usual. If you have your
own fonts installed, however, you need to relocate
your personal mapfiles to .../fonts/map, and run
mktexlsr to update your files database. Also, if
your scripts use kpsewhich, check them."
----------------------------------------------------------------
