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.
Now everything is working fine and slackbuilds are working for texlive.
Quote:
Sun Jul 24 00:30:29 UTC 2016 (...)
office/texlive-extra: Fixed download link and MD5SUM
office/texlive-fonts: Fixed download link and MD5SUM
office/texlive: Fixed some checksums in .info file (...)
and TeXLive 2016 is now at SBo. Thanks for your work on this, franzen - it is *greatly* appreciated!
Quote:
Originally Posted by sombragris
Ok, so now which packages are to be preferred? Franzen's or Robby's?
@sombragris, an case there's confusion, Robby put my buildscripts(which are based on texlive2014 from Robby, by the way) on SBo, so you will get the "same" packages from SBo from
now on.
One nitpick on SBo's scripts: the source downloads are all hosted in what I think is franzen's infrastructure (slackware.schoepfer.info). Can these source packages be mirrored in a more "official" location?
Well, franzen is the maintainer of the texlive package, so it's easier for him to host the necessary tarballs on his own infrastructure - to do otherwise would introduce lots of lag into the process of updates, fixes, etcetera. The script he uses to generate the texmf trees is in the prep/ directory of our texlive git tree, so you can make your own and compare the contents if you're paranoid. I trust his work and will continue to do so absent reason(s) to the contrary.
That said, if e.g. I were to push texlive for inclusion into Slackware, I'd certainly generate the texmf tree myself (as would Pat) and host it on a slackware.com server, but for now, that's an academic point.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.