UPDATE: TexLive 2007 to newer version

[luis.beca@…]

Please update TexLive 2007 (and related packages) to the just released 2008 distribution.

[luis.beca@…]

Cc Me!

[skymoo (Adam Mercer)]

assign to maintainer, reporter is automatically cc'd

[jmroot (Joshua Root)]

Note that the MacPorts version of texlive is based on the OpenBSD version, which has not yet been updated.

[Damien.Pollet@…]

Cc Me!

[tim.lahey@…]

Cc Me!

[vext01@…]

Cc Me!

[vext01@…]

Replying to jmr@…:

Note that the MacPorts version of texlive is based on the OpenBSD version, which has not yet been updated.

Hi,

I am the guy working on this on the OpenBSD side. I am having problems on amd64 at the moment.

I will let you guys know when I have a stable build.

[nathan@…]

Cc Me!

[adfernandes (Andrew Fernandes)]

Cc Me!

[Damien.Pollet@…]

Any news ? Is the BSD AMD build important for updating the port here ?

[macfreek (Freek Dijkstra)]

Cc Me!

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

Cc Me!

[jasper@…]

Cc Me!

[loshea@…]

Cc Me!

[milosh@…]

preliminary tentative for an update

[milosh@…]

I tried updating the texlive port, but no longer having a mac makes it difficult to test it. With help from some testers, I have eliminated some of the problems, but there are still problems that I don't understand:

• even though the --without-ps2eps switch is put, it seems to try to install ps2eps and conflicts with print/ps2eps
• strangely, texlive_base tries to put some files in /opt/local/texmf and /opt/local/texmf-dist instead of /opt/local/share/{texmf,texmf-dist}
• no more minimal variant (sadly)
• not sure tex works after install
• what about tlmgr?
• is the universal_build working (#17555)

If any beta-tester/portfile developper can help, please do.

[aetherknight@…]

Cc Me!

[vinc17@…]

Cc Me!

[(none)]

Milestone Port Updates deleted

[patrickrose@…]

Cc Me!

[nbader@…]

Cc Me!

[anddam (Andrea D'Amore)]

Cc Me!

[earcar@…]

Cc Me!

[earcar@…]

Texlive 2009 is already in prerelease test ​http://www.tug.org/texlive/pretest.html

[vext01@…]

yup, and I am working it on it as we speak. You can take the OpenBSD port as a reference after it's done.

[mroman@…]

maybe the port should base on gentoo texlive ebuild?

[milosh@…]

Replying to mroman@…:

maybe the port should base on gentoo texlive ebuild?

My opinion is no. If you are able to do it, do it. Otherwise, I advise to stick with the "easy" solution (keep the current layout, not creating dozens of new ports, trust openbsd's version to honor destroot).

[jbolden1517@…]

CC Me!

[vext01@…]

Just a note to say, I have not forgotten about the 2009 update (for OpenBSD), I am still awaiting an official release.

Thanks

Edd

[mroman@…]

Cc Me!

[earcar@…]

@edd: TeX Live 2009 and MacTeX 2009 have been released. :)

[vext01@…]

Replying to earcar@…:

@edd: TeX Live 2009 and MacTeX 2009 have been released. :)

Yup, I'm working on it at the moment, but the real world keeps getting in the way.

[milosh@…]

texlive 2009

[milosh@…]

I managed to compile texlive 2009 on a powerbook leopard. The attached file tex.tar.bz2 contains the said hierarchy. Notes:

• xz (needed to uncompress) conflicts with lzmautils
• texlive fails to build with macports' icu
• I only tested no_x11 variant

Some CC=gcc in Makefiles trouble me (afraid they will reopen bug #16916) such as texk/web2c/luatexdir/luamd5/Makefile:CC = gcc

Could someone test it and report status for other configurations?

[milosh@…]

Replying to milosh@…:

Mistake in texlive_base/Portfile: --without-ps2eps should be --disable-ps2eps

[raphael@…]

Cc Me!

[raphael@…]

Replying to milosh@…:

Could someone test it and report status for other configurations?

I tested your TeXLive port on a similar configuration (PM G5, Mac OS X 10.5.8) and it compiled fine but pdflatex was unusable. A new version of the portfiles (and a diff from your version) that produces a working pdflatex binary for me is attached.

The problems I solved are as follows:

• pdflatex tried to look for its configuration files in the wrong directory. (Solution: patch for texmf.cnf)
• Some configure arguments were still wrong and the hashes in front of the icu related arguments were passed to configure so that configure ignored all following arguments.
• At least one format file was wrong. (Solution: call fmtutil-sys --all in post activate phase)

I also tried to compile TeXLive with xindy (therefore I added clisp and ffcall dependencies) but I cannot find any binary belonging to xindy in the result.

Comments and further tests are welcome.

[vext01@…]

Hi Guys,

FYI, I posted a patch for OpenBSD today. There is an issue with package updates, which you may not affect you depending upon how macports deals with collisions and upon which order it will update packages.

This is tested on i386, PPC, SGI, ARM and sparc64.

Note that xindy can only run on i386 and amd64 for OpenBSD due to clisp. You may find this does not affect you.

​http://marc.info/?l=openbsd-ports&m=125960231528532&w=2

I think it is a good thing that we are sharing code and I would be grateful if you report back to me bugs you may find etc.

Thanks

Edd

[vext01@…]

TeX Live 2009 is now in OpenBSD CVS.

[drkp (Dan Ports)]

Cc Me!

[mirimiri66@…]

Cc Me!

[drkp (Dan Ports)]

Well, it's 2010 -- about time to have a working TexLive 2009 package, right? ;-)

I'm currently working on this and hope to have some form of a patch soon. Of course, it all depends on how much time I can shake loose in the next week or two, and just how horrible texlive winds up being.

Ideally I am hoping to divide things up into a few more packages than simply texmf-minimal/full like OpenBSD, though that is always a fallback option.

[robink@…]

Cc Me!

[singingwolfboy@…]

Cc Me!

[mf2k (Frank Schima)]

Cc reporter of dup #23692.

[drkp (Dan Ports)]

Let me say a few words about what I'm working on with the texlive port so that people know what's going on -- looks like there's been a lot of interest in a more recent TeXLive lately.

For background, texlive is a large and lumbering monstrosity. It includes a giant pile of source code (complete with all of its dependent libraries), an even more giant pile of TeX packages, and its own package manager. I believe texlive 2009 is divided into over 3000 packages, which are grouped into about 80 "collections", and further grouped into 10 "schemes".

The version currently in MacPorts is 2007, which IIRC predates TexLive's package management system. So there's a texlive_base port that installs the binaries, a texlive_texmf-full and a texlive_texmf-minimal that install some or all of the tex files, s texlive_texmf-docs port, and a texlive metaport.

This organization doesn't really work for TL 2009, because there's no "minimal" texmf tree anymore and it's not really clear exactly what we'd want to put in a "minimal" install anyway. And I would really rather not support only a full install of texlive, because that's about a gig of distfiles and probably over 2GB installed. Instead, I'd like to provide finer granularity so that users can choose what they want installed.

So my plan is to create the following ports:

• texlive-common, which contains support scripts and files required for building and installing the others (e.g. texmf.cnf)
• texlive-bin, which contains everything built from source (not too different from today's texlive_base)
• one port per texlive collection, e.g. texlive-basic, texlive-latex-recommended, texlive-lang-african

I'm leaning toward one port per collection because I think this is the only option with a decent granularity and a reasonable number of ports. It would wind up creating 80-90 ports, which is a lot, but not totally unreasonable to me. (Note that 30 of these are language-specific packages for 30 languages, and another 24 are documentation in different languages.) This is basically the approach that Debian takes.

The other alternatives are one port per package, which would be great in that you could install exactly the packages you need, but require 3000+ ports, which would be a nightmare. One port per scheme (there are 10 of them) would also be a decent option, except that the schemes overlap, so the ports would conflict. I think one port per collection is the way to go.

I've done a lot of the work necessary for this, including getting the binaries to build and the giant distfile carved up into more manageable collections. I can provide more details if anyone is interested, and I hope to have a patch soon once I get it into reasonably usable shape.

This has been even more of a painful mess than I expected it to be!

[singingwolfboy@…]

Wow, sounds like a lot of work! dports, if you'd like any help, let me know and I'm more than willing to do what I can. Thanks for working on this!

[vext01@…]

The version currently in MacPorts is 2007, which IIRC predates TexLive's package management system. So there's a texlive_base port that installs the binaries, a texlive_texmf-full and a texlive_texmf-minimal that install some or all of the tex files, s texlive_texmf-docs port, and a texlive metaport.

Hi,

I am the OpenBSD TeX Live maintainer, you inherited your original 2007 port from me.

The package manager format did change from 2007 to 2008 from an RDF based format to a text based one. All I had to do was re-write my script which generated the packing lists and I was OK to continue using _base, _texmf-minimal, _texmf-full and _texmf-docs. This is the way I packaged 2008 and 2009 for OpenBSD and it seems to work just fine.

You could probably save yourself some time by stealing my packing lists?

​http://www.openbsd.org/cgi-bin/cvsweb/ports/print/texlive/

Perhaps useful, if not, never mind :)

[luis.beca@…]

How would tlmgr work with this TexLive installation? Would it be able to upgrade packages? Or we'll only be able to upgrade with the usual port mechanism? Thanks

[jabronson@…]

Cc Me!

[aslakr (Aslak Raanes)]

Cc Me!

[drkp (Dan Ports)]

Replying to luis.beca@…:

How would tlmgr work with this TexLive installation? Would it be able to upgrade packages? Or we'll only be able to upgrade with the usual port mechanism? Thanks

I don't think this will (or should be) supported -- having two competing package managers trying to upgrade the same package sounds like a recipe for chaos. This is much like how p5-* ports should be used for perl modules rather than CPAN, etc.

It's perhaps conceivable that you could set up a separate texmf tree that uses tlmgr, but I haven't thought about it.

Were you looking for updates more often than yearly? Or finer-granularity packages? Or something else?

[luis.beca@…]

Were you looking for updates more often than yearly? Or finer-granularity packages? Or something else?

I just got used to TeX Live Utility (​http://code.google.com/p/mactlmgr/) which came with the MacTeX distribution and would like to keep using it to stay up to date.

[drkp (Dan Ports)]

Progress update: I have what I think is close to a working texlive 2009 distribution. This includes successfully building the binaries (which will be the texlive-bin port), the necessary support scripts and config files (this will be texlive-common), and portfiles and distfiles for the texmf packages (~80 ports, one per collection).

So far I've verified basic latex/pdflatex functionality in that I can 'port install texlive-latex-recommended' and then proceed to compile some of my latex documents. I haven't yet tried some of the other tex engines like etex, luatex, xetex, aleph, etc. (I don't use them myself). If you use some of these and wouldn't mind testing a still-somewhat-rough port, drop me an email.

[hypocrite@…]

Cc Me!

[drkp (Dan Ports)]

I'm having some problems with format generation failing right now, but once that's worked out I'll post a preliminary patch for anyone who wants to try it.

This continues to be more complicated than I expect it to be.

[Damien@…]

Cc Me!

[Damien@…]

Replying to dports@…:

Many thanks for your work. A recent TeXlive is indeed very much needed in MacPorts.

So far I've verified basic latex/pdflatex functionality in that I can 'port install texlive-latex-recommended' and then proceed to compile some of my latex documents. I haven't yet tried some of the other tex engines like etex, luatex, xetex, aleph, etc. (I don't use them myself). If you use some of these and wouldn't mind testing a still-somewhat-rough port, drop me an email.

I am currently switching from pdflatex to xelatex, (xetex), so I am quite interested in having it running smoothly.

Also, how do you plan to integrate the extra packages (like MacTeXtras) ?

[mf2k (Frank Schima)]

Cc Me!

[earcar@…]

Cc Me!

[drkp (Dan Ports)]

Ugh. Just upgraded to a 64-bit machine and discovered that xetex doesn't build 64-bit because it uses ATSUI, which is deprecated and unavailable on 64-bit. This doesn't appear to have been solved upstream, either.

Looks like until this is resolved (presumably by a new version of xetex using Core Text) xetex will have to be built 32-bit only. Which means that for now all of the texlive binaries will have to be built 32-bit, since they're all built together.

[drkp (Dan Ports)]

OK, finally: here is a test version of the texlive 2009 port collection. As far as I know everything basically works, though tests especially of xetex, context, etc. would be particularly welcome.

Largest open problem that should be fixed before committing is that it doesn't yet support upgrades from the existing texlive 2007 ports. Also haven't tested how it interacts with other tex ports; sure to be some conflicts.

Other problems I know about that aren't as critical:

• binaries are built 32-bit only because of xetex. This will have to wait for an upstream fix, or somehow split xetex out of the texlive-bin port.
• texlive-bin installs symlinks to some scripts that are in different (optional) packages
• texlive-htmlxml does not build -- I think a format generation problem with jadetex
• some packages may not install cleanly (waiting for post-deactivate hooks)

If you'd like to give it a try, the ports are available at ​http://flute.csail.mit.edu/texports-20100520.tar.gz -- quickest way to get up and running with them is probably to untar the archive and add it as a local repository to macports/sources.conf. For now, you'll need to remove any existing texlive ports before installing. The texlive metaport provides a few variants for different installation schemes (minimal, basic, medium, full), and you can also install ports individually. If upgrading from an earlier texlive install, you might see some errors about ls-R files existing but not being owned by any port; it's safe to forcibly remove these files and retry.

Thanks for help testing!

[drkp (Dan Ports)]

Replying to Damien@…:

Also, how do you plan to integrate the extra packages (like MacTeXtras) ?

As for the MacTeXtras, I'm not really familiar with them. Looking at the contents of the package, it looks like a lot of them are already in MacPorts. Seems best to continue to treat them all as individual ports, though we could consider adding a metaport.

[fracai]

I'm getting an error when trying to install "texlive-basic". I have texports-20100520.tar.gz extracted locally to be installed under my testing prefix ( /Users/arno/Code/macports/development/macports/ ), with no ports installed to start from.

The full debug output is very long, but I can post it if necessary. The end of the attempt is as follows. It appears that /opt/local is being directly referenced somewhere by updmap.

DEBUG: Adding file to file_map: /Users/arno/Code/macports/development/macports/share/texmf-texlive-dist/tex/plain/misc/idxmac.tex for: texlive-basic
DEBUG: Adding file to file_map: /Users/arno/Code/macports/development/macports/share/texmf-texlive-dist/tex/plain/misc/pdfcolor.tex for: texlive-basic
DEBUG: Adding file to file_map: /Users/arno/Code/macports/development/macports/share/texmf-texlive-dist/tex/plain/misc/tugboat.def for: texlive-basic
DEBUG: Adding file to file_map: /Users/arno/Code/macports/development/macports/share/texmf-texlive-dist/tex/plain/misc/xepsf.tex for: texlive-basic
DEBUG: Executing proc-post-org.macports.activate-activate-0
updmap: This is updmap, version $Id: updmap 14402 2009-07-23 17:09:15Z karl $
updmap: no permissions for writing /opt/local/var/db/texmf/web2c/updmap.log', so no transcript
updmap: output directory `/opt/local/var/db/texmf/fonts/map/dvips/updmap' does not exist.
Error: Target org.macports.activate returned: shell command "updmap-sys" returned error 1
DEBUG: Backtrace: shell command "updmap-sys" returned error 1
    while executing
"$post $targetname"
Warning: the following items did not execute (for texlive-basic): org.macports.activate
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

[drkp (Dan Ports)]

Replying to arno+macports@…:

I'm getting an error when trying to install "texlive-basic". I have texports-20100520.tar.gz extracted locally to be installed under my testing prefix ( /Users/arno/Code/macports/development/macports/ ), with no ports installed to start from.

Thanks for testing! I haven't seen that error before, and /opt/local shouldn't be hardcoded anywhere.

I'm wondering if you have an existing texlive or tetex installed in /opt/local, and /opt/local is in your path? If so, it's probably invoking the regular updmap/fmtutil/etc instead of the new one.

I'll deal with this by updating the portgroup to call these programs by their full pathname, but in the meantime you should be able to work around it by making sure your testing prefix is in your PATH before /opt/local.

[fracai]

Cc Me!

[fracai]

Replying to dports@…:

I'm wondering if you have an existing texlive or tetex installed in /opt/local, and /opt/local is in your path? If so, it's probably invoking the regular updmap/fmtutil/etc instead of the new one.

I do have the existing texlive installed under /opt/local, but before I do anything under my testing prefix I run a script to sanitize the environment. It sets the path, for example, to contain only the following, in order:

/Users/arno/Code/macports/development/macports/bin
/Users/arno/Code/macports/development/macports/sbin
/bin
/sbin
/usr/bin
/usr/sbin

Which is why I'm confused as to where the /opt/local is coming from. I just checked 'env' and there isn't a reference anywhere to opt. Very bizarre. Is there a way to get more information about where updmap is being called from and with what options?

The shell script I use before testing:

#!/bin/sh

export MACPORTS=/Users/arno/Code/macports/development/macports

export PATH=/bin:/sbin:/usr/bin:/usr/sbin
export PATH=$MACPORTS/bin:$MACPORTS/sbin:$PATH

export MANPATH=$MACPORTS/share/man

export EDITOR=/usr/bin/nano

export LDFLAGS="-L${MACPORTS}/lib"
export CPPFLAGS="-I${MACPORTS}/include"

export PKG_CONFIG_PATH=$MACPORTS/lib/pkgconfig
export LD_LIBRARY_PATH=$MACPORTS/lib
export LD_RUN_PATH=$MACPORTS/lib

export PYTHONPATH=$MACPORTS/lib/python2.5/site-packages/:$MACPORTS/lib/python2.5/site-packages/gtk-2.0/

[drkp (Dan Ports)]

Oops, you're right, there is a /opt/local hardcoded in texlive-common. Looks like I put the already-patched texmf.cnf in the distfile by mistake.

New version of the distfile is uploaded, and fixed portfiles are available from ​http://flute.csail.mit.edu/texports-20100522.tar.bz2

It also calls updmap and friends via full pathnames, so it might now work even if you have a separate texlive in your path, although I still wouldn't recommend it.

[raimue (Rainer Müller)]

In texlive-bin, build_arch i386 should only be forced on x86_64, on ppc64 it should probably be ppc.

[drkp (Dan Ports)]

Replying to raimue@…:

In texlive-bin, build_arch i386 should only be forced on x86_64, on ppc64 it should probably be ppc.

Good catch, thanks. I told myself earlier to fix that, then proceeded to forget about it.

I have it fixed locally now.

Do you know offhand if ATSUI is unavailable on ppc64 as well as x86_64? I don't have any PPC machines at the moment (and never even used ppc64). I'll test a universal build on a Leopard VM, though.

[drkp (Dan Ports)]

I've moved the portfiles into svn: svn co http://svn.macports.org/repository/macports/users/dports/ports texports will get you the latest copy.

Two major changes since my last post:

• upgrade path for the texlive 2007 ports; it should now be possible to just port upgrade texlive\* (or port upgrade outdated) and end up with a working install of texlive 2009
• post-deactivate hooks: generated format files and other things will be cleaned up when ports are removed.

Both require features in macports 1.9, so you'll need to have that installed.

Open problems that I'm aware of:

• texlive-bin installs symlinks that might be broken if the packages containing their targets aren't installed
• texlive-htmlxml doesn't work yet
• context mark IV is broken (this is an upstream bug w/ TL 2009)
• texlive_bin may not build +no_x11. Might work with poppler +quartz.

I don't think any of these are showstoppers...

[drkp (Dan Ports)]

Committed the texlive 2009 ports in r68883, r68884, and r68885.

Set replaced_by on the old ports in r68886; if you have texlive 2007 installed a port upgrade outdated should work cleanly even though many of the port names changed.

Please let me know if anyone runs into any problems...

[jabronson@…]

Replying to dports@…:

Please let me know if anyone runs into any problems...

I'm having trouble upgrading to the latest texlive due to problems installing libzzip and xmlto (see #27439 and #26151). Any clue what I can do to fix? Just thought I'd ask here in case anyone else has seen this.