A way of extending the PKGTOOLS for handling Groups
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.
Imagine something like a KDevelop in steroids, which is in fact some kind of Control Panel including even a kind of VNC control, for remote servers.
Basically, a Control Panel, and I think that it use some code from KDevelop and NX.
I do not checked what it use precisely from KDE. But does not want to work in your Plasma. I tested it. OK, this was around 2 versions ago.
Then check its dependencies, how hard is that for a seasoned Slackware user. And check how these dependencies can be used alongside Plasma5.
You are being very evasive about this particular software. Are you using it illegally that you do not want to share its name? Or is it developed especially for your company and you are bound by a NDA clause? In which case, why can't you discuss a port to Qt5 with that supplier? Your story makes no sense.
In a way, I understand why the Slackware stay away from automated dependency resolution. It is a can of worms which eats an epic amount of time.
And still you request that the Slackware team creates your coveted "package groups" manually? And of course everyone will demand that every package contained in a group will have all its dependencies met or else all hell breaks loose over broken software in Slackware?
You are a real piece of work. Just try to re-read this entire thread with dry eyes, you will fail miserably.
You and the other few who are all but yelling "elitist" to my face, you really need to get together and create and share something - instead of nodding "good idea" followed by sitting back, waiting for other people to do the hard work. So far I have not seen a line of code or a web site to host that code.
Free tip: instead of trying to get your code (and thus, dependency resolution) into the pkgtools, why don't you write an extension to slackpkg and let that do the work instead? Matteo Rossini did a great job with his slackpkg+, you should be able to do the same.
I tried to explain you how this thing works, at least in my opinion, as a resume.
We all explained to you. The blob works and all the dependencies just do an full install We call them tags and "a" group "ap" group etc. I have my custom group and tags. I did the work. So get your group and tag together and do the work. and have fun. everything works great.
Eric, I explained that my idea is not a dependency resolution, but just an extension of today sets from "single" to "multiple", using a file instead of folders.
A kind of categorization of the packages, not a concept of dependency resolution. You can say even that's exactly the inverse thing.
I even showed an alternative using folders and (sym|hard) links with the similar result. You can find it some pages back.
We all explained to you. The blob works and all the dependencies just do an full install We call them tags and "a" group "ap" group etc. I have my custom group and tags. I did the work. So get your group and tag together and do the work. and have fun. everything works great.
Thanks, I have enough information on this subject to be able to prepare an strategy for my issue.
You and the other few who are all but yelling "elitist" to my face,
Just for record, I re-read the entire thread, looking where someone used to "yell" that you are "elitist", and just like I remembered, no one made that, including me, of course.
Instead, you even received appreciation for the XFCE live, and the rest of the comments was in a civil manner, all of them.
Even the bits of the discussion about "elites" and "elitism" was not for blaming you or someone else. I think other users could confirm.
Last edited by Darth Vader; 12-04-2017 at 06:37 PM.
Nowadays, it's rare to find a harddrive under a couple of hundred GBs, so I imagine very few of us even suspected you had a limit of 15GB. But, having an extremely limited space for installation is a perfectly valid reason to slim down an installation. But, since Slackware doesn't include dependencies, it's not always the easiest thing unlee someone else has already done the work for you.
You've already tried Darth's spin on Alien Bob's XFCE live variant. Another option would be to try Salix. That is a fairly popular distro following the one app per task (I'm not sure if Alien Bob spent much time on this front when he created his variant). Apparently, Salix has three modes: Full, Basic, and Core. They require 2.4GB, 1.4GB and 840MB respectively. Based on what you've posted so far, you'd probably be fine with the Basic mode, which says it will give you: "This installs only a basic desktop environment, with very few extra applications installed on top, such as a web browser and the gslapt package manager. Ideal for advanced users that would like to install a lightweight desktop environment and add their own choice of applications."
Salix is basically Slackware, but with dependency resolution. It is actually binary compatible with Slackware and uses the same package types. So, if you want to try Slackware, but with the features from other distros you've come to expect, Salix might be a good choice for you.
Thanks you, I will try it in the next days.
For now I am "busy" playing with this XFCE live made by Eric Hameleers, installed after Darth's tutorial and it is a full featured desktop. Amazing how many application entered in so small space.
How I am aware that I use what is an experimental installation, not supported either by Slackware, Eric Hameleers or Darth Vader, in the long term I would need to look for a more consistent solution, and this could be Salix.
I written it years ago, in pure C/C++ and use libarchive and libcurl. Maybe should be adjusted for the today GCC.
It use files with syntax like SPEC of RPMBUILD but generate Slackware packages.
No deps handling, but capable to download source files and check their checksum.
I remember you made public the source code of this application years ago, in a thread from this forum, from where I downloaded it myself. Still I have it somewhere.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
