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.
The current branch won't become master until the next stable version of Slackware is released. His repo is a way to keep up with the changes in current so when the next stable is released, official SBo support will be readily available.
As for qt5 support, it's up to the package maintainers if they want to add it. I am keeping several of my SlackBuilds at an older version to not require qt5, python3, and/or gtk3, while others have been updated adding those requirements. The held back packages might be missing some features that newer versions have added, but I didn't deem them important enough to add those extra dependencies. Other maintainers may think for some programs it's worth the extra dependencies for the extra features, and that's their choice.
Yes, we have discussed this on the list. There's some scripts that will be broken if qt5 is updated to newer version because it would require some libraries in Slackware to be upgraded as well which is not going to happen unless security fixes
The current branch won't become master until the next stable version of Slackware is released. His repo is a way to keep up with the changes in current so when the next stable is released, official SBo support will be readily available.
As for qt5 support, it's up to the package maintainers if they want to add it. I am keeping several of my SlackBuilds at an older version to not require qt5, python3, and/or gtk3, while others have been updated adding those requirements. The held back packages might be missing some features that newer versions have added, but I didn't deem them important enough to add those extra dependencies. Other maintainers may think for some programs it's worth the extra dependencies for the extra features, and that's their choice.
I looked at current and there is a ton of stuff many years old that has not been touched. Thus is why I do not touch current. Not Ponces fault the maintainers let things die. Current does not mean latest. It means a separate branch to work on. I have emailed many of the maintainers
with patches only one in the last 5 years got back.
Easier to fork there code be it git hub bitbucket or svn and deal with it. Sbopkg is a wonderful tool. I use.
Quote:
older version to not require qt5
QT5 became a requirement 6 months or so into 14.1 for qjackctl. So I pulled the code and maintain it for 14.1 14.2.. Why in the world would anyone hate slackware that much to break our systems.
The maintainers are not slackers our ldconfig is much simpler. When slackware is based on qt5 I will then put that in my master. Newer is not better it is about being in sync with that version of slackware that way you can set up a devel team for that version stay in sync.
My point of view. Many versions of stuff in the SBO stable should have been held back.
Why qt5 as a requirement in 14.1 is a deal breaker it becomes part of the build system. And the running system.
That means newer version now runs nicely. I will email Edinaldo and see if he is interested in version bumping, although the flacon developer is hinting at a new release soon...
I looked at current and there is a ton of stuff many years old that has not been touched. Thus is why I do not touch current. Not Ponces fault the maintainers let things die. Current does not mean latest. It means a separate branch to work on.
I didn't say it was the latest... his branch is to only make the adjustments to SlackBuilds that needed tweaking to build on Slackware current. Sometimes those adjustments do require installing a newer version of the program, but that isn't always the case.
Quote:
Originally Posted by Drakeo
I have emailed many of the maintainers with patches only one in the last 5 years got back.
Yes, this is a frequent issue on SBo, but if you don't get a response and you're willing to step up, SBo admins will let you take over the maintenance and make whatever changes you want. I've done that for several SlackBuilds. If nobody steps up, then they'll typically stay at whatever version they're currently at unless they start causing problems or someone requests an update.
Quote:
Originally Posted by Drakeo
Easier to fork there code be it git hub bitbucket or svn and deal with it. Sbopkg is a wonderful tool. I use.
This is true. sbopkg works great and it makes it easy to use forked code rather than the default repo.
Quote:
Originally Posted by Drakeo
QT5 became a requirement 6 months or so into 14.1 for qjackctl. So I pulled the code and maintain it for 14.1 14.2.. Why in the world would anyone hate slackware that much to break our systems.
Had you talked to the maintainer about it? Looking at qjackctl's changelog, it looks like qt5 is optional although preferred. Maybe the maintainer would be willing to add a FORCE_QT4 option to the SlackBuild. Or, if you wanted, you could add a qjackctl-qt4 version to SBo. Plenty of python2 SlackBuilds have python3 counterparts, and I don't see why qt couldn't be similar. It's doubtful you're the only one who feels this way about qt5, so others could benefit from this.
Quote:
Originally Posted by Drakeo
The maintainers are not slackers our ldconfig is much simpler. When slackware is based on qt5 I will then put that in my master. Newer is not better it is about being in sync with that version of slackware that way you can set up a devel team for that version stay in sync.
My point of view. Many versions of stuff in the SBO stable should have been held back.
Why qt5 as a requirement in 14.1 is a deal breaker it becomes part of the build system. And the running system.
qt4 has been EOL since 2015. If you look at the Slackware packages, qt-4.8.7 has been used since 2015 with recompiles as needed. Maintainers of SlackBuilds may feel that it is not a good thing to rely on EOL software, so they push up to qt5. This is the maintainer's decision to do and is not something SBo requires or even suggests.
make[1]: Entering directory '/var/tmp/sbo/sbopkg.X2Lwyh/libgnome-2.32.1'
Making all in libgnome
make[2]: Entering directory '/var/tmp/sbo/sbopkg.X2Lwyh/libgnome-2.32.1/libgnome'
GEN stamp-libgnometypebuiltins.h
Traceback (most recent call last):
File "/usr/bin/glib-mkenums", line 688, in <module>
process_file(fname)
File "/usr/bin/glib-mkenums", line 420, in process_file
line = curfile.readline()
File "/usr/lib64/python2.7/codecs.py", line 314, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xa0 in position 3214: invalid start byte
After the recent updates on current, libgda does no longer compile on current; it gives a utf8 error when making the sql-parser:
[...]
same with libgnome; also an utf8-related error
recode:
MD5SUM check for v3.7-beta2.tar.gz ... OK
Building package recode-3.7_beta2-x86_64-2ponce.tgz ... OK
Installing package recode-3.7_beta2-x86_64-2ponce.tgz ... OK
libgda:
MD5SUM check for libgda-5.2.4.tar.xz ... OK
Building package libgda-5.2.4-x86_64-1ponce.tgz ... OK
Installing package libgda-5.2.4-x86_64-1ponce.tgz ... OK
libgnome:
MD5SUM check for libgnome-2.32.1.tar.bz2 ... OK
Building package libgnome-2.32.1-x86_64-2ponce.tgz ... OK
Installing package libgnome-2.32.1-x86_64-2ponce.tgz ... OK
Then, when rebuilding perl-libraries for clam-tk I ran into trouble with perl-cairo: during testing it all stopped on:
Quote:
t/CairoFt.t ....... skipped: need Cairo with FreeType support and Font::FreeType
without perl-cairo, perl-gtk2 and perl-pango do not build either.
I could not find the Font::FreeType module in either perl5 from current Slackbuilds or on SlackBuilds.org.
Using a script based on the perl-Font-AFM slackbuild (see attached) perl-Font-FreeType could be installed, but only
after installing:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
