SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Texlive finally replaced the outdated tetex in the latest current, surely a cause for celebrations!
However, before I replace my own texlive installations, can anyone tell what is included in this package? the source has a readme mentioning that tlmgr isn't included, but I don't know what else is or isn't.
Edit:
Oh, I found it, the prep/texmf_get.sh file in the source directory has all the details
Thanks Patrick, Johannes Schoepfer, and the slackware team for all the hard work,
I am using the texlive distribution, installed from the texlive iso, somewhere out of the /usr tree. Very easy to install. You have just to edit $PATH to make it work. So I will not change to the slackware packages. But maybe for a new install of slackware, I would take the slackware packages.
But I would suggest some minor changes :
- put the extra 3 other texlive packages in the official slackware distribution (maybe they are too big)
- make the slackbuilds work directly with the texlive official tree
Texlive 2017 base package including tikz and Python 3. Slackware next will be a good platform for doing maths stuff on. Nice to see & thanks all involved.
I always try out various distros by seeing if Lyx will correctly display its help files under tools. The old tetex software worked flawlessly in Slackware, but not after texlive was installed. That was the reason I did not use Robby Workmans texlive about a year ago. It is probably only missing one or two sty files.
Oh, I found it, the prep/texmf_get.sh file in the source directory has all the details
To see what's included in slackware-texlive, check /usr/share/texmf-dist/texlive.packages.meta
prep/texmf_get.sh provides names of collections-of-tex-packages(but not the content of theses collections) and single tex-packages, it is not visible what (hard)dependecies are pulled additionally. See texlive.tlpdb for all packages/collections/schemes provided by the texlive netarchives.
Any Lilypond users? Will this affect lilypond in any way? I know with tetex, we haven't been able to build documentation with the slackbuild. Might we actually have documentation again?
Any Lilypond users? Will this affect lilypond in any way? I know with tetex, we haven't been able to build documentation with the slackbuild. Might we actually have documentation again?
Building the lilypond documentation(not the manpage/info) requires the cm-superfonts, afaik.
These fons need about the same space as the whole texlive-core package, so it's not likely to be added. You will need the texlive fonts-package(which includes cm-super) from SBo to build the documentation.
Building the lilypond documentation(not the manpage/info) requires the cm-superfonts, afaik.
These fons need about the same space as the whole texlive-core package, so it's not likely to be added. You will need the texlive fonts-package(which includes cm-super) from SBo to build the documentation.
Johannes
OK, but I shouldn't need anything additional to get lilypond, proper, working? I can live without documentation.
OK, but I shouldn't need anything additional to get lilypond, proper, working? I can live without documentation.
I didn't test, but i think you won't need anything more, than what you need now to build
and run lilypond.
Lilypond 2.18 doesn't need texlive or tetex at compile time(without documentation), and not on run time. Someone wrote me that lilypond 2.19-dev requires the gyre-fonts, and some extra fontconfig. The gyre-fonts are in texlive core package, so that's no problem when lilypond 2.20 is released.
I didn't test, but i think you won't need anything more, than what you need now to build
and run lilypond.
Lilypond 2.18 doesn't need texlive or tetex at compile time(without documentation), and not on run time. Someone wrote me that lilypond 2.19-dev requires the gyre-fonts, and some extra fontconfig. The gyre-fonts are in texlive core package, so that's no problem when lilypond 2.20 is released.
Johannes
Good to know, thanks! I haven't seen any issues since 2002 with texlive in the mailing list archives.
This is very good news. Removing tetex and installing texlive from slackbuilds.org had become a routine post-install operation for me.
Quote:
Originally Posted by Toutatis
But I would suggest some minor changes :
- put the extra 3 other texlive packages in the official slackware distribution (maybe they are too big)
- make the slackbuilds work directly with the texlive official tree
Few people would really need the extra stuff and they take too much space, so it may not be preferable to make the installer ISO considerabley larger for the benefit of a very few. But I completely agree that the extra packages should be available for those who need them. Your second suggestions looks like the best option to me. Instead of 4 out of 4 packages being provided by slackbuilds, it will then be 3 out of 4 --- not much of a change from the current situation.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.