Salix Forums

I am trying to install texlive, but Sourcery complains that "%README%" is missing and I should install it first. Sourcery actually does its job, as SBo's texlive.info file reads: My first guess was I should read the "README" file concerning that package, but there is nothing there relative to dependencies. Furthermore, package texi2html (which is another dependency as stated above), also requires that enigmatic %README% dependency, see texi2html.info in the repos: I guess I am missing something here. Before I force no dependency checking and proceed ignoring %README%, I thought I should ask first. Any tips please?

Things are actually getting more complicated. I decided to force no dependency checking, as the texlive.info file in SlackBuilds.org only mentions the other dependencies and the mysterious %README% dependency is not there::

This requires: texi2html, libsigsegv

So, I installed those dependencies ignoring %README%, then tried to install texlive itself. However, it still doesn't work, complaining about file mismatch: I assumed the Salix repos were not synchronized to the SlackBuilds repos somehow, so I tried again using an alternate slapt-srcrc pointing to the "original" repos. Still no luck, I get the same result as above. Things like slapt-src -e or slapt-src -u won't help either.
Am I doing something wrong here?

No, you're not doing anything wrong. It's just poor maintenance on SBo's part.

The '%README%' "dependency" is SBo's special way of saying you should read the README. And it's at least clumsy.

slapt-src expects everything in the REQUIRES line to be an actual dependency, rightfully. Since it can't find '%README%', it fails.

It seems you haven't discovered another package management tool in Salix, spi. Run for more info. Among other things, spi can handle those weird '%README%' dependencies.
So, texi2html should get installed fine using spi: (I need to add similar checks to sourcery)

The texlive SlackBuild has an additional problem. It's source md5sum does not match the one stated in the info file. That's also something that should be fixed in SBo. But, specifically for texlive, you shouldn't really bother with the SlackBuild. Just get the netinstall script from the texlive webpage:
https://www.tug.org/texlive/acquire-netinstall.html

After you untar it, run the script and install texlive somewhere in your home (I have it in ~/texlive/2014). You could also use somewhere in /opt or anywhere you like actually. Then add the binary location to your PATH in your ~/.bashrc. For example: When a new texlive comes out, repeat the process, install to ~/texlive/2015, delete the old installation and change the PATH. This is far easier and provides a complete installation of texlive. The one from SBo misses tons of stuff.

I also pushed a new package for sourcery-0.9.5 to the repos. It handles the '%README%' dependencies properly. But it only does that for our own copy of the SBo repo. It will still fail if you change the repo to the original SBo one.

You should get the new package as soon as your mirror syncs.

gapan wrote:It seems you haven't discovered another package management tool in Salix, spi. Run

Code: Select all

man spi

for more info. Among other things, spi can handle those weird '%README%' dependencies. So, texi2html should get installed fine using spi:

Code: Select all

sudo spi -i texi2html

(I need to add similar checks to sourcery)

Indeed, I didn't know about spi (I saw it mentioned somewhere but did't really pay attention - my bad). And yes, Sourcery needs spi functionality, when you have time for it.
EDIT: As gapan said, ir's fixed, after last repo sync; Sourcery ignores %README% dependencies now.

The texlive SlackBuild has an additional problem. It's source md5sum does not match the one stated in the info file. That's also something that should be fixed in SBo. But, specifically for texlive, you shouldn't really bother with the SlackBuild. Just get the netinstall script from the texlive webpage:
https://www.tug.org/texlive/acquire-netinstall.html
After you untar it, run the script and install texlive somewhere in your home (I have it in ~/texlive/2014). You could also use somewhere in /opt or anywhere you like actually. Then add the binary location to your PATH in your ~/.bashrc. For example:

Code: Select all

export PATH=$PATH:~/texlive/2014/bin/x86_64-linux

When a new texlive comes out, repeat the process, install to ~/texlive/2015, delete the old installation and change the PATH. This is far easier and provides a complete installation of texlive. The one from SBo misses tons of stuff.

TeXLive netinstall worked perfectly. I just installed it in /usr/local, for system-wide functionality. No real need to use the SBo repo, which is... well, broken (and that's not Salix's fault, apparently).

Thanks again for the valuable information, gapan. I've read about Salix's friendly community in GitHub, and I now know they weren't joking. I mark that thread as "solved" because it really is, and information provided here might help someone else having similar issues.