[SOLVED] Scratching my head. a2x utility missing in Slackware?
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.
Scratching my head. a2x utility missing in Slackware?
I just failed to build on Salix compton. Here's part of log
Code:
a2x --format manpage man/compton.1.asciidoc
make: a2x: command not found
I found on network a2x is a part of AsciiDoc suite http://www.methods.co.nz/asciidoc/a2x.1.html. There is no a2x on Salix repository, no on list of Slackware packages, there is no slackbuild. That's why I am scratching my head
Latest commit for compton was on April 2017. Think it is fresh enough for Slackware 14.2 32 bit. But of course thanks for pointing me to picom. I will have a look for Slackbuild or well build it myself (just getting lazy). At moment I am thinking how to install compton system wide.
I made a slackbuild of Picom and I have been testing it in current. The dependencies aren't bad, but are different than Conky. Functionality is as expected.
I haven't had a chance to test in 14.2, but that's coming up. If it works, I will submit to SBo, but the two issues are (1) the project feels a little "beta" still, although the code seems solid, and (2) it seems like it will conflict with Conky so I'm not sure if it should be packaged independently with a warning or simply replace Conky. Probably the latter, but that's up to them.
I made a slackbuild of Picom and I have been testing it in current. The dependencies aren't bad, but are different than Conky. Functionality is as expected.
Great news. For me xfce looks better with compton running than with xfce native compositor.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.