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.
I have one slackbuild which I submitted because I use the program a lot and it was an orphaned project. I ran it in Slackware-15 a couple of days ago and it built successfully. I doubt if there will ever be any updates provided for it.
Do the majority of former maintainers remember what is that?
It's a must for new script, so they will remember it
For updates, they usually goes through git directly (if they were given access) or via github PR / gitlab MR
for swapinzram, since it is just a rc script with config files
there is no tar.gz as a "source" file
but it is a prerequisite for submissions (as well as md5sum)
But, the source is the tar.gz itself, which makes that the md5 can never match since it is generated after the compression
for swapinzram, since it is just a rc script with config files
there is no tar.gz as a "source" file
but it is a prerequisite for submissions (as well as md5sum)
But, the source is the tar.gz itself, which makes that the md5 can never match since it is generated after the compression
You can look at perf script
it uses dummy source since the source is already on the kernel source
another option is to host the tarball somewhere public and you can compute the checksums
You can look at perf script
it uses dummy source since the source is already on the kernel source
another option is to host the tarball somewhere public and you can compute the checksums
I'm preparing to submit a couple of SlackBuilds, but before I do, I want to make sure all my ducks are in a row...
I seem to be having some trouble with my slack-desc files. Roughly half of my built packages don't display the slack-desc when installing. I've examined these slack-desc files thoroughly and cannot see why some of them don't work. In fact, I have at least one slack-desc (xorg-server-legacy119) that I copied directly from Pat's source, and even that one fails to display the description when installing:
Distribution: Slackware64 {15.0,-current}, FreeBSD, stuff on QEMU
Posts: 452
Rep:
JayByrd, I've seen the missing package description thing when the package names in slack-desc don't match. Trailing spaces don't seem to make a difference, for what it's worth.
I'm preparing to submit a couple of SlackBuilds, but before I do, I want to make sure all my ducks are in a row...
I seem to be having some trouble with my slack-desc files. Roughly half of my built packages don't display the slack-desc when installing. I've examined these slack-desc files thoroughly and cannot see why some of them don't work. In fact, I have at least one slack-desc (xorg-server-legacy119) that I copied directly from Pat's source, and even that one fails to display the description when installing:
i updated sway slackbuild to 1.7 , wlroots to 0.15 , and libseat to 0.6.4 , it would be important that al least wlroots is version 0.15, because new version of river, dwl and other programs that use wlroots depend on wlroots 0.15.
if biker rat dont subbmit a updated version i can submit mine.
edit:
mistake of mine sway 1.7 need meson 0.60+ and older version of sway will do
and slackware 15 use 0.59.4
I've got pretty much all my new ones submitted, but I just realized that I didn't change /bin/sh to /bin/bash on a few. I don't know If I should remove my submission or let it go through at hope the admins catch it and fix it for me. It's only on 3 of the packages I submitted and it doesn't break anything. The three packages are
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.