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.
the script processes the dictionaries from the LibreOffice project. Then I though that others (not only Slackware users) may find these useful, so I put them on my GitHub: https://github.com/slackalaxy/wps-office-dicts
maybe I'll make the SlackBuild just repackage this, since it's much easier...
PS: excellent idea for a thread
Last edited by solarfields; 06-03-2023 at 06:41 AM.
I am at a loss trying to understand the logic of how a thread based on a repackaged feed from an officially endorsed but unofficial third party repository appearing in the official support forum is going to further the demonstration of the distro being alive.
I am at a loss trying to understand the logic of how a thread based on a repackaged feed from an officially endorsed but unofficial third party repository appearing in the official support forum is going to further the demonstration of the distro being alive.
I have the habit of reading LQ. I do not read RSS feeds. Also, here we can discuss the additions. It's as simple as that why I like the thread.
I sometimes do some little tricky stuff but wouldn't it be nice if there was like a « new xxx-tar.gz version » to make ? Like some watching, staying up-to date with some stuff (I think about python modules that get often updated). If there's a thread for it I'd like to know. As I said, I only take the previous SlackBuilds files and change them a little but I'm not so experienced to submit them and moreover to put my name on it. And instead of boring the mainteners with emails... well my two cents.
development/cproc: Added (small C11 compiler).
development/sasm: Added (IDE for NASM,MASM, GAS, and FASM assembly).
games/Mindustry: Added (hybrid tower-defense sandbox factory game)
libraries/googlebenchmark: Added (Google tiny benchmarking library)
libraries/lua53-filesystem: Added (lua filesystem library)
python/python3-aiohttp-oauthlib: Added (aiohttp requests-oauthlib)
python/python3-lazy_loader: Added (Load subpackages and functions)
python/python3-llvmlite: Added (Lightweight LLVM python binding).
python/python3-mir_eval: Added (Music/audio processing algorithms)
python/python3-pooch: Added (A friend to fetch your data files).
python/python3-presets: Added (Manipulate params of module function)
python/python3-soxr: Added (Sample-rate conversion library)
python/python3-videohash: Added (detecting identical videos).
system/libwmf-type1-fonts: Added (postscript fonts for libwmf)
system/pbzx: Added (pbzx stream parser)
This public update brings a lot of python2 removals since they have been ported to python3
or no longer used in any other scripts (willysr)
29 packages removed
Code:
development/pyqt-distutils: Removed (replaced by python3-pyqt-distutils)
development/wheel: Removed (replaced by python3-wheel)
libraries/CherryPy: Removed (replaced by python3-CherryPy)
libraries/plumbum: Removed (replaced by python3-plumbum)
libraries/rpyc: Removed (replaced by python3-rpyc)
libraries/zc.lockfile: Removed (replaced by python3-zc.lockfile)
network/CherryMusic: Removed (replaced by python3-CherryMusic)
network/PyRSS2Gen: Removed (replaced by python3-PyRSS2Gen)
python/APScheduler: Removed (replaced by python3-APScheduler)
python/WTForms: Removed (replaced by python3-WTForms)
python/babelfish: Removed (replaced by python3-babelfish)
python/blinker: Removed (replaced by python3-blinker)
python/cheroot: Removed (replaced by python3-cheroot)
python/docopt: Removed (split into python2/3)
python/guessit: Removed (replaced by python3-guessit)
python/itsdangerous: Removed (replaced by python3-itsdangerous)
python/jaraco.classes: Removed (replaced by python3-jaraco.classes)
python/jsonschema: Removed (replaced by python3-jsonschema)
python/netifaces: Removed (replaced by python3-netifaces)
python/portend: Removed (replaced by python3-portend)
python/pynzb: Removed (replaced by python3-pynzb)
python/python-augeas: Removed (replaced by python3-augeas)
python/python-iso3166: Removed (replaced by python3-iso3166)
python/python-iso639: Removed (replaced by python3-iso639)
python/python3-pep517: Removed (replaced by python3-pyproject-hooks)
python/rebulk: Removed (replaced by python3-rebulk)
python/tempora: Removed (replaced by python3-tempora)
python/zxcvbn-python: Removed (replaced by python3-zxcvbn-python)
system/docker-compose: Removed (replaced by python3-docker-compose)
Last edited by marav; 06-10-2023 at 07:59 AM.
Reason: Fix false positive
system/docker-compose: Removed (replaced by python3-docker-compose)
Thought I'd add a little more context about this one. python3-docker-compose is the last python version and last update for version 1.x.
Anyone familiar with Go want to add a new docker-compose slackbuild for version 2.x? It's a bit of a pain as it wants to download about 500mb during the build.
Otherwise the alienbob pkg for v2 is an option for those that want it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.