SBo scripts not building on current (read 1st post, pls)
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.
Ran into some issues with building openresolve 3.9.2 using the current .SlackBuild
README could not be found
Solved by commenting out line 99 in openresolve.SlackBuild
Code:
#cp README $PKG/usr/doc/$PRGNAM-$VERSION
P.S. I did not try with version 3.9.0 D.S.
I'm the maintainer for openresolv. He must've removed the README (or renamed it to README.md) on the newer versions (the script works fine with the 3.9.0 version it calls). I'll try and push out an update this weekend to SBo for the 3.9.2 version. It wasn't high on my list because the updates were minor.
I'm the maintainer for openresolv. He must've removed the README (or renamed it to README.md) on the newer versions (the script works fine with the 3.9.0 version it calls). I'll try and push out an update this weekend to SBo for the 3.9.2 version. It wasn't high on my list because the updates were minor.
@bassmadrigal Thank you!
I didn't even think of that he could have changed the README file to something else. I did check now, and your guess is correct, it has been renamed README.md
I don't intend to force anyone to do anything, but just suggest something that can benefit users: believe me or not, maybe not worth it for a very small README but a lot of documentation is now provided by upstream projects that is way easier to read as a web pages or pdf documents than in markdown format. Was wrong just mentioning this just as an option?
The wrong thing, is post a command , people CANT execute under slackware if not install some PANDOC ... probably the best is in the readme, "build documentation is an optional but requires install pandoc/pandoc-bin"
If some regular user read your comment ,only go to open ternimal and try execute the command.
Start saying , if have pandoc installed, can do "THIS" .... cause in stock slackware CANT DO THIS.
Last reply , i lost time explaining something too obiously for someone, if you no understand is not my problem....and this thread is not for this. :=)
And of course , you dont force to install pandoc to no one , but post command , only works if installs pandoc ...all right man , but not forced..i can execute pandoc , without installs... ha ha ha , very fun joke. :=)
In this case , i think the best way , is convert the README , and provide ready to use inside de slackbuild.tar kit , as an extra file , converted and ready , thats the best way.
Last edited by USUARIONUEVO; 11-15-2019 at 11:18 PM.
Unfortunately that couldn't be enough as some perl packages might not have perl in their name or other non strictly perl packages might install some perl stuff (as you have discovered with wireshark).
How can I recognize which 3-rd party software (only from SBo repo are in my system) that must be recompiled ?
There is some odd ball mismatch going on:
I can't build Inkscape 1.0 on my -current and when i try run the prebuilt one from ponce's repo i get missing ImagMagick6 error while -current is running an I.M.-7 package
There is some odd ball mismatch going on:
I can't build Inkscape 1.0 on my -current and when i try run the prebuilt one from ponce's repo i get missing ImagMagick6 error while -current is running an I.M.-7 package
FWIW it started when i only referenced the missing symlinks
Working fine here so far (@ 74% and still going). Was loads of dependencies to sort, but I skipped the libwpd one as it was not required.
I've seen nothing related to ImageMagick so far...
Running current 64-bit updated as of a couple of hours ago. Are you running 32-bit current? (shouldn't matter though, me thinks)
Just to clarify one thing, Inkscape 1.0 is BETA1, is 0.92.4 building ok for you?
Edit:
And now there's an error (3 actually) of missing files... INSTALL, NEWS and GPL*.txt
INSTALL -> INSTALL.md
NEWS -> NEWS.md
GPL*.txt -> New structure in the tar.bz2 file. All Licenses are found in its own folder LICENSES:
GPL-2.0-or-later.txt
GPL-2.0.txt
GPL-3.0-or-later.txt
GPL-3.0.txt
LGPL-2.1-or-later.txt
LGPL-2.1.txt
LGPL-3.0-or-later.txt
LGPL-3.0.txt
MPL-1.1.txt
Edited the inkscape.SlackBuild file, line 102 to be
AUTHORS COPYING* INSTALL.md NEWS.md README* TRANSLATORS doc/* \
Removed GPL and it built just fine
Last edited by MDKDIO; 11-16-2019 at 05:33 PM.
Reason: Edit part...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.