Slackware 15 just dropped yesterday after a 6 year gap and I'm wondering if anyone here uses it knows how well supported it is. I know two folks on Matrix who do, but the way they talk the Slackbuilds by Ray-V are rather shallow.
I'm thinking of using Slackware myself because of its incredible resistance to change (much like TDE) But, if Trinity is not well supported I don't know how it will go. I don't care for any of the desktop environments or window managers that come with it. For me it's either TDE, icewm, or nothing.
My main machine is running Slackware64-current. I do most of TDE relevant development there.
Ray-V's slackbuilds are stable and work really well, occasional bugs notwithstanding, but some apps might not have slackbuilds (it's not a "package everything" approach).
I actually have a slackbuild generator script I use for building apps not in Ray-V's slackbuild collection and for development purposes. If there is interest I could publish it somewhere (probably on my Github). It is somewhat hacky but works well enough for most purposes (just not core packages, Ray-V's slackbuilds are just better).
-- Philippe
On February 4, 2022 3:32:09 PM CST, Mavridis Philippe mavridisf@gmail.com wrote:
My main machine is running Slackware64-current. I do most of TDE relevant development there.
Awesome, I didn't know any developers used it. I wanted to know if this would be something future proof if I ever get into development.
I actually have a slackbuild generator script I use for building apps not in Ray-V's slackbuild collection and for development purposes. If there is interest I could publish it somewhere (probably on my Github). It is somewhat hacky but works well enough for most purposes (just not core packages, Ray-V's slackbuilds are just better).
Funnily enough, we were just talking about having more Slackbuilds in my TDE Matrix room! Indeed there are Slack users interested in getting more applications so that would be great.
Hello and sorry for the late reply,
I have published my SlackBuilds generator for TDE on GitHub. Please read the README before using it. I haven't tested it on pretty much anything but my main Slackware64-current machine, so you can expect bugs. You can also expect it to fail with some error I had not foreseen. I don't plan to spend much time, but I'm open to feedback and I will accept bug reports (contributions are even more welcome ;-))
https://github.com/blu256/tde-slackbuild-gen
Use it to build packages not provided by Ray-V's SlackBuilds and make sure you specify the correct path settings based on where you installed TDE (I tested mostly with the /usr prefix).
Instructions: 1. Clone the repository of your chosen package or otherwise obtain its source code. 2. Run `./gentdesb <dir>`, where <dir> is the directory where the source code is stored (e.g. ` ./gentdesb mathemagics`, if your source code is in a directory named "mathemagics" under the current directory). 3. You will be prompted for some basic information (paths, build type). 4. gentdesb will generate an appropriate SlackBuild based on your input and the detected build system for the package. You are advised to actually take a look at the generated SlackBuild, just for safety (no, don't worry, I haven't sneaked a `rm -rf /` in there). 5. Run the generated SlackBuild (e.g.`./mathemagics.SlackBuild`) 6. Install the generated package (e.g. `installpkg /tmp/mathemagics-git-x86_64-1_tde.tgz`). Its name will be reported by the SlackBuild when the build finishes.
-- Philippe
I just made my first successful Slackware installation last night, one purpose hoped for which was to run TDE on it. Before I can do that, I have all to learn about its package management system. I gave it the maximum space I ever give a test installation, 8GB, and only have 1.2G freespace remaining after limiting installation to A, AP, KDE, L, N, X, XAP, which I hoped would leave around half the filesystem in freespace. I have a lot of removing to do before I can try adding TDE to it. :(
-
Felix Miata -
Hunter Ellett -
Mavridis Philippe