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.
OK. I finally got it reproduce. For this error, since it is for the log file, so no output at all.
1. If you have texlive-remainder installed, no error.
2. Removing the texlive-remainder package still give no error.
3. I remove all texlive package and remove all remaining directory /usr/share/texmf-var /usr/share/texmf-config/,
only have /usr/share/texmf/tex/latex/gnuplot/gnuplot.cfg left over as that is from gnuplot.
remove ~/.texlive2015
4. re-install texlive-20150521-x86_64-2jsc.
5. Then problem appear.
Thanks for your help, texi2any should now work without the remainder-package.
Also xelatex/context is more usable now. The new packages are as usual here.
Unfortunately, after upgrade to texlive-20150521-x86_64-4jsc, still got the same problem.
Damn, maybe i didn't fetch the newest created texmf-tree. For testing i removed the package, , ~/.texlive* and ~/texmf, but forgot /usr/share/texmf-* as there are new files generated on runtime. Anyway, new (current)package is uploaded.
Bad news, I have another 2 machines with current, after cleanup all previous install of texlive, the problem comes back again with texlive-20150521-x86_64-5jsc, it seems I did not do a proper clean up when testing 5jsc. (It does not work even with texlive-remainder-20160315-noarch-1jsc.txz)
Another suggestion, could the package do proper cleanup when un-install? it seems it left quite a few things behind.
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,644
Rep:
Quote:
Originally Posted by qunying
Another suggestion, could the package do proper cleanup when un-install? it seems it left quite a few things behind.
Slackware package tools don't have pre-install or pre-/post-removal routines like Debian or others have. You would have to write a script yourself to do the house-keeping I guess.
The installation from the texlive distribution seems much more simple. You can put everything in one directory, modify $PATH in an appropriate way. And to unisntall, simply delete the directory.
The installation from the texlive distribution seems much more simple. You can put everything in one directory, modify $PATH in an appropriate way. And to unisntall, simply delete the directory.
I don't feel that this is much more simple than "installpkg texlive...txz".
- ~/.texlive2015 also will appear
-The installation will be way bigger
-You'll be on your own watching for updates
There are several ways to get texlive installed, this thread is about developing a "small" texlive slackware package.
The problem with uninstallation is mainly about debugging the strange texinfo effects with the small buid. Normaly you may want to keep /usr/share/texmf-{local,var} on upgrading.
@franzen In fact I install everything in texlive (now 5GB !)
texlive has its own update manager (tlmgr). But contrary to slackware, you have to uninstall everything when a new version appears every year, and install the new version. This is the main defect I think, but this may change in the future.
@franzen In fact I install everything in texlive (now 5GB !)
Keep in mind that many Slackware users don't use or need the full texlive; so in that way what Franzen is trying to achieve is very useful and to be applauded as Tex that comes as default is no longer maintained. Moreover even those that use the full texlive, like myself, might prefer one that is integrated with the rest of the system. I'm looking forward to the result...
@moesasji I am sure that a small texlive package would be useful. But it is also true that not all users have the same needs. So perhaps you should need different packages.
Bad news, I have another 2 machines with current, after cleanup all previous install of texlive, the problem comes back again with texlive-20150521-x86_64-5jsc, it seems I did not do a proper clean up when testing 5jsc. (It does not work even with texlive-remainder-20160315-noarch-1jsc.txz)
Good news, new working package(s) are up. The package was brocken by an poppler-upgrade in "current".
"URW Base 35" fonts added.
Here I have to install -remainder because at least this: "! LaTeX Error: File `pgfcore.sty' not found."
pdflatex is included without -remainder package, for netfilter.tex the texpackage pgf(600kb) is needed, which i added in the latest current package. "pdflatex netfilter.tex" now works without -remainder package.
The current package did also grow as i added some packages to test ConTEXt.
pdflatex is included without -remainder package, for netfilter.tex the texpackage pgf(600kb) is needed, which i added in the latest current package. "pdflatex netfilter.tex" now works without -remainder package.
The current package did also grow as i added some packages to test ConTEXt.
Yep, outstanding. Best I can tell, this works with all of the .tex files I have locally - great job!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
