Gnome 42.0: Dark Mode Style does not work

[slackernetuk]

Hiya guys,

the work is done, all scripts to build Gnome 42 are online. I had to modify some scripts and I added gnome-background & gnome-terminal as well. The most things working nicely but there a little complication....to turn on the dark mode does not work.

Maybe someone can help to fix it.

Scripts: https://gitlab.com/slackernetuk/gnome-light/-/tree/Current-42.0

Binaries -current https://slackernet.ddns.net/slackware/slackware64-current/slackware64/gnome-light/42.0/

[rizitis]

When you have new binaries plz upload here. Also give us a feed back, what was missing. :))

[slackernetuk]

New binaries for Gnome 42 / Slackware -current are online

libportal and xdg-desktop-portal-gtk were missing.

Just for a change, I also added a script to install the new Fedora 36 wallpapers.

[rizitis]

Arch have first beta unstable release , there is a new arch patch for GDM https://gitlab.com/fabiscafe/gnome-unstable/-/blob/main/gdm/0001-Xsession-Don-t-start-ssh-agent-by-default.patch I add it to my pacth and to slackbuld script, everything ok, although that gdm still dont run ...for me.

[slackernetuk]

Arch have first beta unstable release , there is a new arch patch for GDM https://gitlab.com/fabiscafe/gnome-unstable/-/blob/main/gdm/0001-Xsession-Don-t-start-ssh-agent-by-default.patch I add it to my pacth and to slackbuld script, everything ok, although that gdm still dont run ...for me.

Thank you for pointing that out! I think to get run gdm on Slackware would be my next challenge. Fingers crossed ;-)

[rizitis]

good luck !!!!

ps If you decide to fight with the devil... keep this on your /tmp you may need it...

[fulalas]

@slackernetuk, I haven't tried your packages but on Porteus (the distro I work on that is based on Slackware) dark mode works just nice. Gonna try on Slackware 15 live later on.

1. you don't need gnome-terminal because it has been replaced by gnome-console which is already present in your base :)
2. why are you installing libportal and xdg-desktop-portal-gtk? In my tests they are not necessary.
3. GDM is pure bullshit. I wouldn't invest my time on it if I were you. It doesn't do well even the most basic thing it's supposed to: switching between different desktop environments. Try to do that in distros that use GDM. And, my lord, how can something be this slow?!
4. Cristina Mansur doesn't need to be credited because she is not a developer but Raphael Fabeni's girlfriend (that's why he thanked her) LOL

[fulalas]

No problems :)

Have you tried in Slackware 15.0? Maybe the issue you're seeing is related to Slackware current, which I haven't tried.

[slackernetuk]

@slackernetuk, I haven't tried your packages but on Porteus (the distro I work on that is based on Slackware) dark mode works just nice. Gonna try on Slackware 15 live later on.

1. you don't need gnome-terminal becase it has been replaced by gnome-console which is already present in your base :)
2. why are you installing libportal and xdg-desktop-portal-gtk? In my tests they are not necessary.
3. GDM is pure bullshit. I wouldn't invest my time on it if I were you. It doesn't do well even the most basic thing it's supposed to: switching between different desktop environments. Try to do that in distros that use GDM. And, my lord, how can something be this slow?!
4. Cristina Mansur doesn't need to be credited because she is not a developer but Raphael Fabeni's girlfriend (that's why he thanked her) LOL

Honestly, I don't like 'gnome-console', too simple for my needs. By the way, 'gnome-console' isn't a 'Gnome-Terminal' replacement.

    We are not however trying to replace GNOME Terminal/Tilix, these advanced 
    tools are great for developers and administrators, rather Console aims to serve 
    the casual linux user who rarely needs a terminal

But, I can see your point...to modify the build script with a parameter would be good compromise.

Possibly 'libportal' isn't necessary,but without 'xdg-desktop-portal-gtk' the style switcher doesn't work on Slackware current. 'xdg-desktop-portal-gtk' is a backend implementation for xdg-desktop-portal using GTK.

What shall I say, the German perfectionism is a bit strange...sometimes. :laughing: Anyway, maybe I should mention my wife as well.....she makes very good coffee. :rofl:

[fulalas]

GNOME is such a mess, hahaha! In the official release note they say:

GNOME’s default apps is the set of apps that GNOME recommends be included in a default GNOME installation. For GNOME 42, we have two new apps in the default app set: Text Editor and Console.

It's so odd that Slackware current requires xdg-desktop-portal-gtk but Slackware 15.0 doesn't. I'm about to test it in Current and then I can tell you :)

Anyway, maybe I should mention my wife as well.....she makes very good coffee.

LOL

[fulalas]

Indeed, in Slackware current I end up in that lovely GNOME shell error screen. But that was using my GNOME 42 binaries. Let's see with yours.

EDIT: using your binaries:

[fulalas]

So, yes, for some reason Slackware current requires xdg-desktop-portal-gtk in order to have light/dark modes working. But it doesn't need libportal.

[rizitis]

I had successfully hack google-online-account so goa-daemon is runing if I want, only if its needed as dependency from other apps-service during compiling , whithout really working as informer... but dependency is satisfied lol

[rizitis]

baobab rhythmbox grilo totemplparser

[slackernetuk]

Hiya guys, GNOME 42.0 binaries for Slackware 15.0 are online.....wasn't a big deal...I just had to upgrade gnome-icon-theme package.

@rizitis congrats & great stuff!

[fulalas]

Nice work, @slackernetuk! :)

BTW, have you managed to solve this?

[fulalas]

Maybe you guys want to read my GNOME 42 review :)

https://medium.com/@fulalas/gnome-42-the-nonsense-continues-7d96c3287f7

[rizitis]

bash-5.1# ./power-profiles-daemon-mailn.SlackBuild 
power-profiles-daemon-main/
power-profiles-daemon-main/.editorconfig
power-profiles-daemon-main/.gitignore
power-profiles-daemon-main/.gitlab-ci.yml
power-profiles-daemon-main/COPYING
power-profiles-daemon-main/NEWS
power-profiles-daemon-main/README.md
power-profiles-daemon-main/check-news.sh
power-profiles-daemon-main/data/
power-profiles-daemon-main/data/meson.build
power-profiles-daemon-main/data/net.hadess.PowerProfiles.conf.in
power-profiles-daemon-main/data/net.hadess.PowerProfiles.policy
power-profiles-daemon-main/data/net.hadess.PowerProfiles.service
power-profiles-daemon-main/data/power-profiles-daemon.service.in
power-profiles-daemon-main/docs/
power-profiles-daemon-main/docs/meson.build
power-profiles-daemon-main/docs/power-profiles-daemon-docs.xml
power-profiles-daemon-main/docs/power-profiles-daemon-sections.txt
power-profiles-daemon-main/docs/power-profiles-daemon.types
power-profiles-daemon-main/docs/version.xml.in
power-profiles-daemon-main/meson.build
power-profiles-daemon-main/meson_options.txt
power-profiles-daemon-main/src/
power-profiles-daemon-main/src/meson.build
power-profiles-daemon-main/src/net.hadess.PowerProfiles.xml
power-profiles-daemon-main/src/power-profiles-daemon.c
power-profiles-daemon-main/src/power-profiles-daemon.gresource.xml
power-profiles-daemon-main/src/power-profiles-daemon.h
power-profiles-daemon-main/src/powerprofilesctl.in
power-profiles-daemon-main/src/ppd-action-trickle-charge.c
power-profiles-daemon-main/src/ppd-action-trickle-charge.h
power-profiles-daemon-main/src/ppd-action.c
power-profiles-daemon-main/src/ppd-action.h
power-profiles-daemon-main/src/ppd-driver-fake.c
power-profiles-daemon-main/src/ppd-driver-fake.h
power-profiles-daemon-main/src/ppd-driver-intel-pstate.c
power-profiles-daemon-main/src/ppd-driver-intel-pstate.h
power-profiles-daemon-main/src/ppd-driver-placeholder.c
power-profiles-daemon-main/src/ppd-driver-placeholder.h
power-profiles-daemon-main/src/ppd-driver-platform-profile.c
power-profiles-daemon-main/src/ppd-driver-platform-profile.h
power-profiles-daemon-main/src/ppd-driver.c
power-profiles-daemon-main/src/ppd-driver.h
power-profiles-daemon-main/src/ppd-enums.c.in
power-profiles-daemon-main/src/ppd-enums.h.in
power-profiles-daemon-main/src/ppd-profile.c
power-profiles-daemon-main/src/ppd-profile.h
power-profiles-daemon-main/src/ppd-utils.c
power-profiles-daemon-main/src/ppd-utils.h
power-profiles-daemon-main/tests/
power-profiles-daemon-main/tests/integration-test.py
power-profiles-daemon-main/tests/meson.build
power-profiles-daemon-main/tests/unittest_inspector.py
The Meson build system
Version: 0.59.4
Source dir: /tmp/SBo/power-profiles-daemon-main
Build dir: /tmp/SBo/power-profiles-daemon-main/_build
Build type: native build
Project name: power-profiles-daemon
Project version: 0.10.1
C compiler for the host machine: ccache cc (gcc 11.2.0 "cc (GCC) 11.2.0")
C linker for the host machine: cc ld.bfd 2.37-slack15
Host machine cpu family: x86_64
Host machine cpu: x86_64
Compiler for C supports arguments -fgnu89-inline: YES 
Compiler for C supports arguments -Wundef: YES 
Compiler for C supports arguments -Wunused: YES 
Compiler for C supports arguments -Wstrict-prototypes: YES 
Compiler for C supports arguments -Werror-implicit-function-declaration: YES 
Compiler for C supports arguments -Wno-pointer-sign: YES 
Compiler for C supports arguments -Wshadow: YES 
Found pkg-config: /usr/bin/pkg-config (0.29.2)
Run-time dependency gio-2.0 found: YES 2.73.0
Run-time dependency gudev-1.0 found: YES 237
Run-time dependency upower-glib found: YES 0.99.17
Run-time dependency polkit-gobject-1 found: YES 0.120
Program xmllint found: YES (/usr/bin/xmllint)
Configuring config.h using configuration
Found pkg-config: /usr/bin/pkg-config (0.29.2)
Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources)
Program glib-mkenums found: YES (/usr/bin/glib-mkenums)
Program python3 found: YES (/usr/bin/python3)
Configuring powerprofilesctl using configuration
Configuring power-profiles-daemon.service using configuration
Configuring net.hadess.PowerProfiles.conf using configuration
Program python3 found: YES (/usr/bin/python3)
Program unittest_inspector.py found: YES (/tmp/SBo/power-profiles-daemon-main/tests/unittest_inspector.py)
Program check-news.sh found: YES (/bin/sh /tmp/SBo/power-profiles-daemon-main/check-news.sh)
Program /tmp/SBo/power-profiles-daemon-main/check-news.sh found: YES (/bin/sh /tmp/SBo/power-profiles-daemon-main/check-news.sh)
Build targets in project: 6

Option buildtype is: release [default: debugoptimized]
Found ninja-1.10.2 at /usr/bin/ninja
Generating targets:   0%|                                                     |                                                                                 Writing build.ninja:   0%|                                                   | 0                                                                                
ninja: error: loading 'build.ninja': No such file or directory

Good news are that probably I found a solution to pass systemd dependency, but I am not sure because I have this meson bug ... Can you help me to find a solution for this?

edit: the error on the slackbuild name(mailn) is ok, I dont want tgz package to be created now... if script run ok untill that stage...

[rizitis]

https://github.com/rizitis/Gnome42-Slackware-15.0-STABLE/tree/main/power-profiles-daemon

thats the best I can do... :)

[slackernetuk]

Nice work, @slackernetuk! :)

BTW, have you managed to solve this?

Not yet....but rizitis solution seems alright....sadly, I just can test stuff by QEMU/KVM at the moment.

[slackernetuk]

https://github.com/rizitis/Gnome42-Slackware-15.0-STABLE/tree/main/power-profiles-daemon

thats the best I can do... :)

I have modified your scripts, have a look and tell me what you think. :relaxed:

-Dsystemdsystemunitdir is just the path to the systemd service file. We need this meson option just to build power-profiles-daemon without systemd, we start the daemon with rc.local anyway. We should delete the systemd stuff when power-profiles.daemon is built? rm -rf $PKG/usr/lib/systemd

[rizitis]

I builded it with -D systemdsystemunitdir=false\ some other options for other systemd apps are: -D admin_group=wheel \ -D introspection=false \ -D elogid=false \ -D systemd=false \ You have to look the source of every app and see what of all those options maybe is userful...

If you want command grep systemd /var/log/packages/* and you will find that lots of programs provide those .service files but since you dont have systemd on your Slackware thats all fake news... So for my opinion dont need to rm -rf .... but I am not expert... Also PAT never said that Slackware will be systemd free disrto for ever... (I hope we will never go to systemd system but...) , so I really dont know the answer for you question... I also have installed google-online-accounts daemon but I cant find right now my scripts, I will search again today if I found them I will upload them also. The only reason I build that bullshit daemon is that some other programs need it as dependency ONLY for building :P So I run him on background on terminal and when build finish I just kill him...

[slackernetuk]

I builded it with -D systemdsystemunitdir=false\ some other options for other systemd apps are: -D admin_group=wheel \ -D introspection=false \ -D elogid=false \ -D systemd=false \ You have to look the source of every app and see what of all those options maybe is userful...

If you want command grep systemd /var/log/packages/* and you will find that lots of programs provide those .service files but since you dont have systemd on your Slackware thats all fake news... So for my opinion dont need to rm -rf .... but I am not expert... Also PAT never said that Slackware will be systemd free disrto for ever... (I hope we will never go to systemd system but...) , so I really dont know the answer for you question... I also have installed google-online-accounts daemon but I cant find right now my scripts, I will search again today if I found them I will upload them also. The only reason I build that bullshit daemon is that some other programs need it as dependency ONLY for building :P So I run him on background on terminal and when build finish I just kill him...

I don't know, maybe you misunderstood, what I have written earler. The point is, to build 'power-profiles-daemon' on Slackware we need the -D systemdsystemunitdir option....but /usr/false isn't a valid place for systemd-service files.

Just have a look into /usr/lib/systemd/system or /lib/systemd/system

By the way, to delete the power-profiles-daemon.seriveis just an opinion.

BTW, it wasn't a technical question, I just wanted to know your opinion. :smile:

[rizitis]

I am sorry , I m using google translate... I try hard with my (non) English... :(

btw: I have a problem with https://gitlab.com/slackernetuk/gnome-light/-/tree/Current-42.0/xdg-desktop-portal-gtk I am trying to install it on slackware.15 stable wich allready have 1.12.1 version but Slackbuild script fails...

configure: error: Package requirements (xdg-desktop-portal >= 1.14.0 glib-2.0 >= 2.44 gio-unix-2.0 gtk+-3.0 >= 3.14 gtk+-unix-print-3.0) were not met:

Requested 'xdg-desktop-portal >= 1.14.0' but version of xdg-desktop-portal is 1.12.1

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

if you have any suggestion plz... Greek language are welcome also :D

ps It very important to find a solution to be working "record desktop" because its the only app for record desktop properly on Wayland... we must found what is missing... How you will make the installation video on youtube? ;) I installed gnome 40 from your video first time, I didnt knew about Rafael gfs github... :)

[rizitis]

If you open dconf editor there not option for screenrecord it should be an option max-screencast-length at this path... there is the place that you can edit how long screen record can record as maximum time, but we dont have screen record installed :(

also from terminal if command gsettings set org.gnome.settings-daemon.plugins.media-keys max-screencast-length 14400

No such key “max-screencast-length”

but since its part of gnome desktop the app why we all have the same problem? Something is missing...

[slackernetuk]

I am sorry , I m using google translate... I try hard with my (non) English... :(

btw: I have a problem with https://gitlab.com/slackernetuk/gnome-light/-/tree/Current-42.0/xdg-desktop-portal-gtk I am trying to install it on slackware.15 stable wich allready have 1.12.1 version but Slackbuild script fails...

configure: error: Package requirements (xdg-desktop-portal >= 1.14.0 glib-2.0 >= 2.44 gio-unix-2.0 gtk+-3.0 >= 3.14 gtk+-unix-print-3.0) were not met:

Requested 'xdg-desktop-portal >= 1.14.0' but version of xdg-desktop-portal is 1.12.1

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

if you have any suggestion plz... Greek language are welcome also :D

ps It very important to find a solution to be working "record desktop" because its the only app for record desktop properly on Wayland... we must found what is missing... How you will make the installation video on youtube? ;) I installed gnome 40 from your video first time, I didnt knew about Rafael gfs github... :)

If you want build Gnome 42 on Slackware 15.0 following this steps.

git clone https://gitlab.com/slackernetuk/gnome-light.git -b 15.0-42.0
cd gnome-light
./build.sh

If you prefer the gnome-terminal instead of gnome-console GT=yes ./build.sh

Oh, 'xdg-desktop-portal-gtk' is just necessary on Slackware -current.....is this bloody GNOME mess. :laughing:

I have some Greek friends but I don't speak Greek at all, but German is welcome as well. :rofl:

Screencasting on Wayland is 'obs' or 'obs-gnome-screencast' probably the best choice

[adcdam]

@slackernetuk it would be nice if you submit the packages to Sbo.

[rizitis]

Ι have localy upgrade all slackport/gfs scripts to the latest release of every version. Untill Monday I hope I finsh. GDM included :p

[adcdam]

well it woud be nice if someone submit the slackbuilds to slackbuilds.org although i dont use Gnome some user will like to have gnome, i submitted slackbuilds but nothing related to gnome.

[rizitis]

You are right, but the problem is that sbo scripts have very special writing typo, and they will not approved my typo of script... 13 packages only canot be build to latest version from gfs because of bugs ... I will try again Monday and then I will upoload everything... I will try to pull request first slackport/gfs , thats the first thing...

[adcdam]

https://slackbuilds.org/templates/ just adapt the slackbuilds to the suggested new templates, i did that for my slackbuilds its very easy but it takes time.

[rizitis]

https://www.linuxquestions.org/questions/slackware-14/gnome-for-slackware-gnome-from-scratch-gnome-40-2-a-4175698008/#post6346635

Also now i can install extensions from the site. Everything works fine except gdm and screen record. But to be honest, gnome is a big dependency confusio... To build it we need to upgrade, downgrade lots of libs... Every app need other version of the same lib 🤒

[adcdam]

now that all is working as it should including gdm ( i saw the slackware post) if you want to submit the packages you have to create README, slack-desc, slackbuilds and the package.info files for every package, maintain the Rafael Tavares name in the slackbuilds. if you want you can email me so i can help you to speed up because now its a tedious thing of typing a lot. perhaps you can ask fulalas and slackernetuk for some help too. By the way you mention that you are a farmer what do you cultivate? can you send some pics?

[rizitis]

Ok @adcdam I will sent you all scripts that was not modified but work as it was or the only change was the number of version. You can convert them to the sbo way... The others I will keep them because need a lot of work to write it clear and only me knows what i have done... When I finsh I will rewrite them the sbo way also... But there are already lots of those scripts on sluckbuilds.org so before you work with them check and if missing from sbo then write it... I dont believe that gnome slackbuilds will be accepted on sbo but we can try....

Yew I m a farmer, a poor farmer. I have olives trees and I product olive oil. Also for my family I have on summer vegetables... These photos are 10 - 15 years old , you can take a look of our land .. I m not on photos , I was the photografer :) https://www.flickr.com/photos/rizitis/albums/72157626752913539

[rizitis]

@adcdam @slackernetuk these scripts I dont have to send them via email because you can take them directly from slackports/gfs Dont need update , because no new versions has been on those repositories. gfs scripts works fine for those files and are still up to date ... So @slackernetuk if you want to put something from those in your project is ready @adcdam if you want to work with some of these files for slackbuilds you are ready to do it... I will not work with them...

ps sorry for the path... just read the last words before "okold", the name of file as it is on slackports/gfs

/home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/Vulkan-Headers/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/Vulkan-Tools/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/alabaster/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/apparmor/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/appstream-glib/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/avahi/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/blocaled/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/brasero/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/clutter/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/clutter-gst/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/clutter-gtk/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/cogl/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/constantly/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/cssselect/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/cunit/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/cups-pk-helper/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/cython/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/dbus-test-runner/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/dog/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/funcsigs/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/gnome-games/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/gnome-user-share/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/gnome-video-effects/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/gom/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/gspell/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/gtk-frdp/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/gtkspell3/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/jam/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/jq/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/libaccounts-glib/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/libchamplain/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/libcloudproviders/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/libdaemon/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/libdmapsharing3/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/libgdata/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/libgrss/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/libiptcdata/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/libisoburn/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/libisofs/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/libjte/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/libmanette/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/libmediaart/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/libmusicbrainz5/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/libovf-glib/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/libpst/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/libquvi-scripts/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/libstemmer/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/libuchardet/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/liburcu/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/libzapojit/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/luajit/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/memphis/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/mypy_extensions/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/oath-toolkit/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/pyelftools/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/python-webencodings/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/python2-scandir/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/rest/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/sanlock/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/smartypants/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/sphinx/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/sphinx_rtd_theme/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/sphinxcontrib-jsmath/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/sphinxcontrib-qthelp/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/telepathy-glib/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/telepathy-mission-control/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/tepl/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/totem-pl-parser/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/tracker-miners2/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/tracker-miners3/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/typogrify/okold /home/all1/Documents/Slackbuilds/gnomebuilds/rafael-gnome/source/uhttpmock/okold

[slackernetuk]

@rizitis Let's be honest, Rafael has done a really good job, but I think I will rewrite all scripts to the SBo standard.

[rizitis]

@rizitis Let's be honest, Rafael has done a really good job, but I think I will rewrite all scripts to the SBo standard.

Yes thats exactly what I m doing now. Rafael has done GREAT job, but I m writing all scripts I kept (not those "okold" thats for @adcdam ) to the sbo way. If you want guys we can organize our job so we dont do double work.. I really dont care if my name is as modifier on scripts. I know very well how to write a script on the sbo way, its the only thing I know well... If you guys want to separate the job , it will be fine for me, if you want to work alone, thats ok for me also... I m here for your and for the comunity, if I can do something plz tell me.

[rizitis]

I want to say one more, from the files I kept to work the sbo way , 99 files are already to sbopkg, even if are not up to date, we CANT send them to SlackBuilds, because they dont accept packages who someone else maintain , even if those packages are not updated. We have to email the maintainer fist and if he accept we must send the email we received from him to SlackBuilds and after that we can send the scripts updated to SlackBuilds. I will not do that. I will write only scripts that are not in SBo and I will send them. If they approve them ok, if not no problem for me... Thats the list of SBo packages that have maintainer from scripts I kept... forget that RRR at the end...

/home/all1/SlackportGnm42/source/Automat/RRR /home/all1/SlackportGnm42/source/ConfigParser/RRR /home/all1/SlackportGnm42/source/Jinja2/RRR /home/all1/SlackportGnm42/source/MarkupSafe/RRR /home/all1/SlackportGnm42/source/acpica/RRR /home/all1/SlackportGnm42/source/argyllcms/RRR /home/all1/SlackportGnm42/source/audit/RRR /home/all1/SlackportGnm42/source/babeltrace/RRR /home/all1/SlackportGnm42/source/cantarell-fonts/RRR /home/all1/SlackportGnm42/source/devhelp/RRR /home/all1/SlackportGnm42/source/elixir/RRR /home/all1/SlackportGnm42/source/enchant2/RRR /home/all1/SlackportGnm42/source/evince/RRR /home/all1/SlackportGnm42/source/exempi/RRR /home/all1/SlackportGnm42/source/file-roller/RRR /home/all1/SlackportGnm42/source/flake8/RRR /home/all1/SlackportGnm42/source/flatpak/RRR /home/all1/SlackportGnm42/source/flatpak-builder/RRR /home/all1/SlackportGnm42/source/freerdp/RRR /home/all1/SlackportGnm42/source/geoclue2/RRR /home/all1/SlackportGnm42/source/glusterfs/RRR /home/all1/SlackportGnm42/source/gspell/RRR /home/all1/SlackportGnm42/source/gssdp/RRR /home/all1/SlackportGnm42/source/gtest/RRR /home/all1/SlackportGnm42/source/gtk-vnc/RRR /home/all1/SlackportGnm42/source/gtksourceview4/RRR /home/all1/SlackportGnm42/source/gtkspell3/RRR /home/all1/SlackportGnm42/source/html5lib/RRR /home/all1/SlackportGnm42/source/hyperlink/RRR /home/all1/SlackportGnm42/source/imagesize/RRR /home/all1/SlackportGnm42/source/incremental/RRR /home/all1/SlackportGnm42/source/jam/RRR /home/all1/SlackportGnm42/source/leveldb/RRR /home/all1/SlackportGnm42/source/lgi/RRR /home/all1/SlackportGnm42/source/libcacard/RRR /home/all1/SlackportGnm42/source/libgit2/RRR /home/all1/SlackportGnm42/source/libgit2-glib/RRR /home/all1/SlackportGnm42/source/libgusb/RRR /home/all1/SlackportGnm42/source/libgxps/RRR /home/all1/SlackportGnm42/source/libhandy/RRR /home/all1/SlackportGnm42/source/liboauth/RRR /home/all1/SlackportGnm42/source/libosinfo/RRR /home/all1/SlackportGnm42/source/libpeas/RRR /home/all1/SlackportGnm42/source/libportal/RRR /home/all1/SlackportGnm42/source/libpst/RRR /home/all1/SlackportGnm42/source/librdkafka/RRR /home/all1/SlackportGnm42/source/libseccomp/RRR /home/all1/SlackportGnm42/source/libvirt-glib/RRR /home/all1/SlackportGnm42/source/libwpe/RRR /home/all1/SlackportGnm42/source/lxml/RRR /home/all1/SlackportGnm42/source/mm-common/RRR /home/all1/SlackportGnm42/source/more-itertools/RRR /home/all1/SlackportGnm42/source/mypy/RRR /home/all1/SlackportGnm42/source/ostree/RRR /home/all1/SlackportGnm42/source/pathlib2/RRR /home/all1/SlackportGnm42/source/perl-Text-CSV/RRR /home/all1/SlackportGnm42/source/phodav/RRR /home/all1/SlackportGnm42/source/pluggy/RRR /home/all1/SlackportGnm42/source/plymouth/RRR /home/all1/SlackportGnm42/source/protobuf/RRR /home/all1/SlackportGnm42/source/py/RRR /home/all1/SlackportGnm42/source/pycodestyle/RRR /home/all1/SlackportGnm42/source/pyflakes/RRR /home/all1/SlackportGnm42/source/pytest-runner/RRR /home/all1/SlackportGnm42/source/python3-astroid/RRR /home/all1/SlackportGnm42/source/python3-attrs/RRR /home/all1/SlackportGnm42/source/rabbitmq-c/RRR /home/all1/SlackportGnm42/source/rabbitmq-server/RRR /home/all1/SlackportGnm42/source/rest/RRR /home/all1/SlackportGnm42/source/seahorse/RRR /home/all1/SlackportGnm42/source/setuptools-scm/RRR /home/all1/SlackportGnm42/source/simple-scan/RRR /home/all1/SlackportGnm42/source/snappy/RRR /home/all1/SlackportGnm42/source/snowballstemmer/RRR /home/all1/SlackportGnm42/source/sphinx_rtd_theme/RRR /home/all1/SlackportGnm42/source/sphinxcontrib-applehelp/RRR /home/all1/SlackportGnm42/source/sphinxcontrib-devhelp/RRR /home/all1/SlackportGnm42/source/sphinxcontrib-htmlhelp/RRR /home/all1/SlackportGnm42/source/sphinxcontrib-serializinghtml/RRR /home/all1/SlackportGnm42/source/spice/RRR /home/all1/SlackportGnm42/source/spice-gtk/RRR /home/all1/SlackportGnm42/source/spice-protocol/RRR /home/all1/SlackportGnm42/source/typed_ast/RRR /home/all1/SlackportGnm42/source/uncrustify/RRR /home/all1/SlackportGnm42/source/usbredir/RRR /home/all1/SlackportGnm42/source/valgrind/RRR /home/all1/SlackportGnm42/source/webkit2gtk/RRR /home/all1/SlackportGnm42/source/wheel/RRR /home/all1/SlackportGnm42/source/wpebackend-fdo/RRR /home/all1/SlackportGnm42/source/xdg-dbus-proxy/RRR /home/all1/SlackportGnm42/source/xdg-desktop-portal/RRR /home/all1/SlackportGnm42/source/xdg-desktop-portal-gtk/RRR /home/all1/SlackportGnm42/source/xmlsec/RRR /home/all1/SlackportGnm42/source/yajl/RRR /home/all1/SlackportGnm42/source/yelp/RRR /home/all1/SlackportGnm42/source/yelp-tools/RRR /home/all1/SlackportGnm42/source/yelp-xsl/RRR /home/all1/SlackportGnm42/source/zenity/RRR /home/all1/SlackportGnm42/source/zope.interface/RRR

[adcdam]

rizitis about slackbuilds.org they do accept updates from someone else but you ll have to ask the mantainer first.

[rizitis]

We have to email the maintainer first and if he accept...

@adcdam yes thats what I wrote^^ :)

[adcdam]

someone post in the slackware forum posted this

i couldnt recommend this at all. theres not much explanation for this link in particular. slackernet.ddns.net/slackware/,

for anyone reading this stick with gfs and if you want to get closer to bleeding edge, use another distro or do it from scratch with a build system probs gfs 8-D

wow fantastic that user recommend to use another distro for gnome. what a nice community....

[rizitis]

We can write that we have gnome running on our slackware64 and we are very happy...

[rizitis]

@adcdam I m to old to play games... so I ask on irc #slackbuilds

Topic for #slackbuilds set by willysr!~willysr@sbopkg/willysr (Sat Apr 16 08:48:17 2022)

hello, I have one question, if i write SlackBuilds scripts for Gnome 42 DE , apps libs everything I had and use, is this approved for SlackBuilds or since Slackware official dont provide Gnome dont need them and I will lost my time? thank you.

if they dont answer yes, I will not lose my time... I m online now and waiting...

[rizitis]

Urchlay> r-tz: we wouldn't reject it just because it's gnome. we already have some gnome components on SBo even: https://slackbuilds.org/result/?search=gnome&sv=15.0

The answer is yes!

[rizitis]

the one problem you might have: the gnome stuff on SBo is probably way too old for gnome 42. you'd have to either version-update it (if that doesn't break anything that depends on it) or submit the new versions under new script names (so the old versions can stay as-is)

e.g. libgnome is version 2.32.1, and has been since 2011. https://slackbuilds.org/advsearch.php?stype=revdep&q=libgnome <--- shows a list of builds that depend on libgnome if you wanted to update libgnome to a new version, you'd have to make sure all those builds still work with it. or, you'd have to invent a new name like "libgnome42" or "libgnome-gnome42" for your new version and it probably would conflict with the existing libgnome, so you'd have to mention that fact in your README

[slackernetuk]

@rizitis Let's be honest, Rafael has done a really good job, but I think I will rewrite all scripts to the SBo standard.

Yes thats exactly what I m doing now. Rafael has done GREAT job, but I m writing all scripts I kept (not those "okold" thats for @adcdam ) to the sbo way. If you want guys we can organize our job so we dont do double work.. I really dont care if my name is as modifier on scripts. I know very well how to write a script on the sbo way, its the only thing I know well... If you guys want to separate the job , it will be fine for me, if you want to work alone, thats ok for me also... I m here for your and for the comunity, if I can do something plz tell me.

Just my opinion, if everyone is cooking their own soup...it's a waste of time.

I think the project needs a bit more structure and I think Gitlab isn't the best platform to talk about the details.

Maybe a small management tool for software projects would be better to talk about the details.

By the way, are you guys on Facebook?

[rizitis]

By the way, are you guys on Facebook?

No i dont have facebook or any other socials...

this is the dialog I had we the slackbuild team

r-tz: we wouldn't reject it just because it's gnome. we already have some gnome components on SBo even: https://slackbuilds.org/result/?search=gnome&sv=15.0 Urchlay thank you very much for the answer, we are 3 people with the same idea, but first we want ask! thank you. the one problem you might have: the gnome stuff on SBo is probably way too old for gnome 42. you'd have to either version-update it (if that doesn't break anything that depends on it) or submit the new versions under new script names (so the old versions can stay as-is) e.g. libgnome is version 2.32.1, and has been since 2011. https://slackbuilds.org/advsearch.php?stype=revdep&q=libgnome <--- shows a list of builds that depend on libgnome if you wanted to update libgnome to a new version, you'd have to make sure all those builds still work with it. or, you'd have to invent a new name like "libgnome42" or "libgnome-gnome42" for your new version and it probably would conflict with the existing libgnome, so you'd have to mention that fact in your README ok I understand.. thank you. just for information , I have stable and current Slackware64 on 2 different pc and everything works fine, even gdm... I upgrade all libraries but I use TAGS... yeah I think another problem as well is that there are different maintainers for a lot of these components. It's hard to really put out a GNOME platform and desktop release unless you have full control over shipping all of the components as well. By the time you corralled all of the maintainers to sync up the components for, say, GNOME 42, GNOME 43 would probably be out ;) poprocks, yes you right, the main idea is that if someone want Gnome 42, he can have it from SBo and not from "my" gitlab, github... and yes we dont have to follow Gnome releases... that is the point for other distros not our distro... but since we dont have conflicts , it will be nice for slackers the opportunity to download and build from our SBo... at least we can try, I have all scripts ready but now i must rewrite them the SBo standard. I think everything ll go fine..if not ok we try.. :) I hear what you're saying, but I think ever since slackware dropped GNOME some 15+ years ago, there's been a general consensus in the community that if one wants to run a GNOME desktop on slackware, one is best off using a spinoff distro like dropline, dlackware and the like - and sbo is more focused on providing some GNOME applications to primarily run on other WMs and DEs ok I understand, I will re-write them if for some serious reasons that guys of SlackBuilds knows (better than me) not approve them its not a problem. Some off them it will be useful for other reasons except Gnome DE... :)

but i agree that this is not the right place for talking... if you think a solution that we can speak as a team it would be nice.. this issue here should be close...

[adcdam]

i think that slackernetuk is right i agree on "if everyone is cooking their own soup...it's a waste of time". The first thing is to check is that gnome 42 can work well with Slackware 15 i mean im my pc i use current with gtk4-4.6.2 but slackware 15 use version 4.4.1 (i didnt tested with that version) and you cant change that. I did my own version using gtk4-4.6.2 but what i did is useless and can t be sent to slackbuilds.org because of the version of gtk4 that i used (or that if what i think). you can ask the guys at the irc of slackbuilds. Then if everything work as it should i mean it work perfect with both x11 and wayland, gdm work as it should and dark mode works then its only a matter of porting and cleaning the slackbuilds to the slackware standards, and making the info, readme and slack-desc files and submit them also ask the maintainers of some slackbuilds that need updating. i have no horse in this race but it would be nice if gnome is available in Slackbuilds.org, i dont have any problems in helping here.

if im mistaken please correct me specially the part about gtk4 version.

[rizitis]

Ok then we all agree, so i think that slackernetuk should take the risk to be the "leader" and organise the job. First of all we have to find a place to talk. This issue must close...

[adcdam]

first please check if im mistaken or not about the gtk4 version.

[slackernetuk]

Ok then we all agree, so i think that slackernetuk should take the risk to be the "leader" and organise the job. First of all we have to find a place to talk. This issue must close...

Firstly, I'll make a rough plan and then let you guys know which direction we could take.

I prefer to talk about the details by mail....if you guys have better ideas let me know.

By the way, Linux from Scratch has updated to GNOME42 as well.....very helpful for dependencies, patches etc.