Requests for current-next (15.0-->15.1)

gmgf · 03-20-2022, 07:51 PM

Quote:

Originally Posted by marav

Code:

--enable-kernel=VERSION compile for compatibility with kernel
                        not older than VERSION

from ./configure --help

that's it.

marav · 03-21-2022, 06:01 AM

Since lua has become an increasingly necessary dependency for many projects.
Like mpv, vlc, obs, wireshark, conky, ... (more than 100 projects on SBo)

Can we expect to have it in slackware?

saxa · 03-21-2022, 06:31 AM

gtk-4.6.2
https://download.gnome.org/sources/g...k-4.6.2.tar.xz

pango-1.50.6
https://download.gnome.org/sources/p...-1.50.6.tar.xz

franzen · 03-21-2022, 12:32 PM

Quote:

Originally Posted by marav

Can we expect to have it in slackware?

In theory, it's already there

Code:

texlua --credits | grep 'lua version'
Compiled with lua version 5.3.6

Code:

cat <<EOF>hello.lua
print("Hello World!"
EOF
texlua --luaonly hello.lua 
Hello World!

But i have no idea to what extend it's usable as real lua interpreter.

Tonus · 03-21-2022, 12:53 PM

Quote:

Originally Posted by marav

Since lua has become an increasingly necessary dependency for many projects.
Like mpv, vlc, obs, wireshark, conky, ... (more than 100 projects on SBo)

Can we expect to have it in slackware?

I believe it's not too simple as (like with python earlier ?) some projects are for lua5.1, or 5.4 and anything in between. I had a few modified slackbuilds that made SBo builds install along each others but I guess that's the maintainers' job.

Anyway I would like it (I could have both luakit and neomutt lua capability without lot of work <3 )

xunilq · 03-21-2022, 01:28 PM

I'm on 15.0 after a few years away from linux and i'm honestly surprised as i have not logged on my windows account since i have installed 15.0 a week ago. Managed to install everything i had on windows for gaming and productivity with superior performance and now added excitement.

edited, i was even more off topic

marav · 03-22-2022, 02:52 AM

Quote:

Originally Posted by Tonus

I believe it's not too simple as (like with python earlier ?) some projects are for lua5.1, or 5.4 and anything in between. I had a few modified slackbuilds that made SBo builds install along each others but I guess that's the maintainers' job.

Anyway I would like it (I could have both luakit and neomutt lua capability without lot of work <3 )

According to the documentation, versions < 5.4 will not be upgraded anymore
https://www.lua.org/versions.html

So, It doesn't cost much to keep them, eventually in extra/, and to have the latest stable in the main tree

Thom1b · 03-22-2022, 06:47 AM

Hi,
It seems rubygem-asciidoctor needs to be rebuilt against ruby-3.1.1.

Before rebuilding it:

Code:

# asciidoctor -v
/usr/lib64/ruby/3.1.0/rubygems.rb:265:in `find_spec_for_exe': can't find gem asciidoctor (>= 0.a) with executable asciidoctor (Gem::GemNotFoundException)
        from /usr/lib64/ruby/3.1.0/rubygems.rb:284:in `activate_bin_path'
        from /usr/bin/asciidoctor:23:in `<main>'

After rebuilding:

Code:

# asciidoctor -v
Asciidoctor 2.0.15 [https://asciidoctor.org]
Runtime Environment (ruby 3.1.1p18 (2022-02-18 revision 53f5fc4236) [x86_64-linux]) (lc:UTF-8 fs:UTF-8 in:UTF-8 ex:UTF-8)

teoberi · 03-22-2022, 07:01 AM

Samba 4.16.0

Markus Wiesner · 03-22-2022, 07:30 AM

Quote:

Originally Posted by Thom1b

Hi,
It seems rubygem-asciidoctor needs to be rebuilt against ruby-3.1.1.

That could be combined with an update to asciidoctor 2.0.17

Didier Spaier · 03-22-2022, 07:33 AM

Quote:

Originally Posted by Thom1b

Hi,
It seems rubygem-asciidoctor needs to be rebuilt against ruby-3.1.1.

Before rebuilding it:

Code:

# asciidoctor -v
/usr/lib64/ruby/3.1.0/rubygems.rb:265:in `find_spec_for_exe': can't find gem asciidoctor (>= 0.a) with executable asciidoctor (Gem::GemNotFoundException)
        from /usr/lib64/ruby/3.1.0/rubygems.rb:284:in `activate_bin_path'
        from /usr/bin/asciidoctor:23:in `<main>'

After rebuilding:

Code:

# asciidoctor -v
Asciidoctor 2.0.15 [https://asciidoctor.org]
Runtime Environment (ruby 3.1.1p18 (2022-02-18 revision 53f5fc4236) [x86_64-linux]) (lc:UTF-8 fs:UTF-8 in:UTF-8 ex:UTF-8)

Not sure about this one. Arch builds asciidoctor-2.0.17 against ruby-3.0.3. Maybe the respective building methods make a difference here? In any case if this is actually a ruby version issue, it should be reported upstream (i.e. to Dan Allen), I think.

PS And maybe a ruby upgrade will break existing gems? Not a concern for Slackware which ships only one AFAIR, but for me it would be one as Slint64-15.0 will include 26. OK, rather rhethorical argument as it will not be based on -current...

PPS Confirmed. Quick and dirty build (on Slackware64-15.0) inspired from https://github.com/archlinux/svntogi...trunk/PKGBUILD gives:

Code:

~$ asciidoctor -v
Asciidoctor 2.0.17 [https://asciidoctor.org]
Runtime Environment (ruby 3.0.3p157 (2021-11-24 revision 3fb7d2cadc) [x86_64-linux]) (lc:UTF-8 fs:UTF-8 in:UTF-8 ex:UTF-8)

EDIT: works also with 2.0.15: "Qui peut le plus, peut le moins." (not always true with computer programs, though.)

USUARIONUEVO · 03-22-2022, 08:44 AM

@Didier Spaier

Archlinux remains under ruby-3.0 cause some gems not ready for 3.1 thats all.

If ascdoctor builds under 3.1.1 then we can go.

Some gens i see not build native extensions under ruby 3.1 , but slackware only have 1 , if nothing break , we safe , if not safe we see on build time as "error"

Didier Spaier · 03-22-2022, 09:03 AM

@USUARIONUEVO: Whether it be or not the right time to upgrade ruby in Slackware-current is not a concern for me, I just pointed out that this upgrade is/was not necessary to build asciidoctor.

USUARIONUEVO · 03-22-2022, 09:35 AM

sorry but asciidoctor is ruby , not PYTHON.

you say that

Not sure about this one. Arch builds asciidoctor-2.0.17 against ruby-3.0.3

And i clarify , arch not move to ruby-3.1 cause some gems not ready.

But slackware for now only have asciidoctor gem , if build, then no problem to go 2.0.15 , 2.0.17 or 2.0.30000000000

Didier Spaier · 03-22-2022, 12:16 PM

Quote:

Originally Posted by USUARIONUEVO

sorry but asciidoctor is ruby , not PYTHON.

Corrected, thanks.

Quote:

you say that

Not sure about this one. Arch builds asciidoctor-2.0.17 against ruby-3.0.3

And i clarify , arch not move to ruby-3.1 cause some gems not ready.

But slackware for now only have asciidoctor gem , if build, then no problem to go 2.0.15 , 2.0.17 or 2.0.30000000000

I have already answered that I do not care which ruby versions is shipped in -current that I do not use.