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

marav · 05-11-2024, 11:41 AM

Quote:

Originally Posted by sombragris

Well, about my request to switch to Plasma 6, I still think it's appropriate. I know that Pat intended to have 15.1 with Plasma 5, but I think criterion was set under the vague expectation of a release date that would have been closer to 15.0 release than it is now.

I'm in no hurry to see any release at all, but I would have liked to have Slackware stable shipped with a reasonably current, mature and stable version of the Plasma desktop.

I support whatever Pat decides on the matter; but if (for example) we get a LTS Plasma 6 version before the next Slackware stable release, I think switching to Plasma 6 would be best.

About Plasma 6 LTS:

Code:

No scheduled LTS releases yet. 
If distributions find LTS releases useful, 
we will schedule those in close cooperation 
with the corresponding distributions.

https://community.kde.org/Schedules/Plasma_6

glennmcc · 05-11-2024, 03:10 PM

Patrick,

Just a heads-up for if and when you decide to upgrade gFTP to the current code at
https://github.com/masneyb/gftp be it built for GTK+2 or GTK+3

The configuration files are now being placed in ~/.config/gftp

Therefore, to continue using ~/.gftp, one line of code needs to be changed in lib/misc.c

Code:

/*  BASE_CONF_DIR = g_build_filename (g_get_user_config_dir(), "gftp", NULL);*/
  BASE_CONF_DIR = g_build_filename (g_get_home_dir(), ".gftp", NULL);

In addition, the ignore_pasv_address= configuration option no-longer exists in the new code.

Therefore, each user will need to remove or at-least comment-out this section in their ~/.gftp/gftprc file.

Code:

# If this is enabled, then the remote FTP server's PASV IP address field will
# be ignored and the host's IP address will be used instead. This is often
# needed for routers giving their internal rather then their external IP
# address in a PASV reply.
ignore_pasv_address=0

And of-course to build for GTK+3 instead of GTK+2
simply add 2 more configuration options to the slackbuild script.

Code:

--disable-gtk2 \
--enable-gtk3 \

After making those changes, the new code works 100% perfectly on -current
and it retains the previous configuration from before the upgrade.

Jeebizz · 05-12-2024, 12:56 PM

Quote:

Originally Posted by sombragris

Well, about my request to switch to Plasma 6, I still think it's appropriate. I know that Pat intended to have 15.1 with Plasma 5, but I think criterion was set under the vague expectation of a release date that would have been closer to 15.0 release than it is now.

I'm in no hurry to see any release at all, but I would have liked to have Slackware stable shipped with a reasonably current, mature and stable version of the Plasma desktop.

I support whatever Pat decides on the matter; but if (for example) we get a LTS Plasma 6 version before the next Slackware stable release, I think switching to Plasma 6 would be best.

maybe he could put a version in /testing for 15.1 at least , so that would be something i guess? is AlienBob again picking up the slack (no pun intended) for plasma6?, just hopefully this time it doesn't take as long as Plasma5 to be included even in to --current at some point.

ponce · 05-12-2024, 03:48 PM

Quote:

Originally Posted by ponce

when/if your sources won't build because of it don't forget to have a look at the handy "porting to" page...

looking at the gazillion of fixes Pat had to do for gcc 14.x I doubt that stuff on SBo won't need a similar treatment...

https://git.slackware.nl/current/commit/?id=abc3e67

mistfire · 05-13-2024, 02:29 AM

Is it possible to add wsdd on slackware repo?

WSDD is a Web Services Dynamic Discovery host daemon. Starting Windows 10 Build 1707 NetBIOS device discovery was disabled in favor of Web Service Dynamic Discovery.

Starting GVFS 1.54 (which was the current version in the slackware packages) Web Services Dynamic Discovery was implemented for viewing nearby computer and NAS on the networks. However it uses wsdd as backend which was not available on slackware repo.

Could you please add wsdd on the slackware repo?

There are two wsdd programs to choose from

wsdd source code: https://github.com/christgau/wsdd
This was written in python

wsdd2 source code: https://github.com/Netgear/wsdd2
This was written in C but it requires to create a symlink named wsdd pointed to wsdd2 executable or renamed wssd2 executable as wsdd

saxa · 05-13-2024, 05:57 AM

libxml2-2.12.7
https://download.gnome.org/sources/l...-2.12.7.tar.xz

gwhl · 05-13-2024, 06:43 AM

Quote:

Originally Posted by glennmcc

Patrick,

Just a heads-up for if and when you decide to upgrade gFTP to the current code at
https://github.com/masneyb/gftp be it built for GTK+2 or GTK+3

The configuration files are now being placed in ~/.config/gftp

Therefore, to continue using ~/.gftp, one line of code needs to be changed in lib/misc.c

Code:

/*  BASE_CONF_DIR = g_build_filename (g_get_user_config_dir(), "gftp", NULL);*/
  BASE_CONF_DIR = g_build_filename (g_get_home_dir(), ".gftp", NULL);

[…]

The new behavior is correct in that it brings compliance with https://specifications.freedesktop.o...ec-latest.html in line with lots/most of maintained software nowadays.

glennmcc · 05-13-2024, 08:36 AM

Quote:

Originally Posted by gwhl

The new behavior is correct in that it brings compliance with https://specifications.freedesktop.o...ec-latest.html in line with lots/most of maintained software nowadays.

So, all of these are non-compliant ?

Code:

~/.adobe
~/.dbus
~/.ddd
~/.distlib
~/.dosbox
~/.dvdcss
~/.eboard
~/.fontconfig
~/.fonts
~/.gconf
~/.gftp
~/.gimp-2.8
~/.gnupg
~/.gphoto
~/.gvfs
~/.hplip
~/.java
~/.links
~/.local
~/.macromedia
~/.mozilla
~/.mplayer
~/.ocp
~/.pki
~/.qdvdauthor
~/.qt
~/.sane
~/.scim
~/.soma
~/.ssh
~/.ssr
~/.subversion
~/.thumbnails
~/.wicd
~/.xine
~/.xmms
~/.xpaint
~/.zenmap
~/.bash_history
~/.fim_history
~/.isomaster
~/.lesshst
~/.wget-hsts
~/.Xauthority
__________________

All (or at-least most), of them should be moved into ~/.config/ ?

ZhaoLin1457 · 05-13-2024, 09:37 AM

Quote:

Originally Posted by glennmcc

So, all of these are non-compliant ?

Yes.

Quote:

Originally Posted by glennmcc

Code:

~/.adobe
~/.dbus
~/.ddd
~/.distlib
~/.dosbox
~/.dvdcss
~/.eboard
~/.fontconfig
~/.fonts
~/.gconf
~/.gftp
~/.gimp-2.8
~/.gnupg
~/.gphoto
~/.gvfs
~/.hplip
~/.java
~/.links
~/.local
~/.macromedia
~/.mozilla
~/.mplayer
~/.ocp
~/.pki
~/.qdvdauthor
~/.qt
~/.sane
~/.scim
~/.soma
~/.ssh
~/.ssr
~/.subversion
~/.thumbnails
~/.wicd
~/.xine
~/.xmms
~/.xpaint
~/.zenmap
~/.bash_history
~/.fim_history
~/.isomaster
~/.lesshst
~/.wget-hsts
~/.Xauthority
__________________

All (or at-least most), of them should be moved into ~/.config/ ?

Let's not be more Catholic than the Pope, as the Debianites are...

mistfire · 05-13-2024, 09:44 AM

Quote:

Originally Posted by glennmcc

So, all of these are non-compliant ?

Code:

~/.adobe
~/.dbus
~/.ddd
~/.distlib
~/.dosbox
~/.dvdcss
~/.eboard
~/.fontconfig
~/.fonts
~/.gconf
~/.gftp
~/.gimp-2.8
~/.gnupg
~/.gphoto
~/.gvfs
~/.hplip
~/.java
~/.links
~/.local
~/.macromedia
~/.mozilla
~/.mplayer
~/.ocp
~/.pki
~/.qdvdauthor
~/.qt
~/.sane
~/.scim
~/.soma
~/.ssh
~/.ssr
~/.subversion
~/.thumbnails
~/.wicd
~/.xine
~/.xmms
~/.xpaint
~/.zenmap
~/.bash_history
~/.fim_history
~/.isomaster
~/.lesshst
~/.wget-hsts
~/.Xauthority
__________________

All (or at-least most), of them should be moved into ~/.config/ ?

technically speaking most of them are not compliant (~/.local was XDG standard). that's why unofficial gtk+3 port of isomaster config file was moved to ~/.config folder.

gmgf · 05-13-2024, 09:48 AM

And if you put them in the trash, they come back

r1w1s1 · 05-13-2024, 10:16 AM

Firefox 126
https://ftp.mozilla.org/pub/firefox/releases/126.0/

glennmcc · 05-13-2024, 10:29 AM

OK then... after an upgrade to the new gFTP,
in order to retain the settings from the previous version, each user will need to...

mkdir ~/.config/gftp
cp -r --preserve=all ~/.gftp/* ~/.config/gftp/
rm -r ~/.gftp

Or perhaps...

mv ~/.gftp ~/.config/gftp

_____

I can imagine that it would quite difficult for the slackware package doinst.sh script
to do that for all users on the system upon upgrading to the new version.

____

There we go, made a suggestion at github.

https://github.com/masneyb/gftp/issues/180

rizitis · 05-13-2024, 01:40 PM

Quote:

Originally Posted by glennmcc

OK then... after an upgrade to the new gFTP,
in order to retain the settings from the previous version, each user will need to...

mkdir ~/.config/gftp
cp -r --preserve=all ~/.gftp/* ~/.config/gftp/
rm -r ~/.gftp

Or perhaps...

mv ~/.gftp ~/.config/gftp

_____

I can imagine that it would quite difficult for the slackware package doinst.sh script
to do that for all users on the system upon upgrading to the new version.

____

There we go, made a suggestion at github.

https://github.com/masneyb/gftp/issues/180

Just an idea for doinst.sh idk if it work but as base idea i think its good

Code:

#!/bin/sh

OLD_CONFIG_DIR="/home/*/.gftp"
NEW_CONFIG_DIR="/home/*/.config/gftp"

migrate_config() {
    for user_dir in $OLD_CONFIG_DIR; do
        if [ -d "$user_dir" ]; then
            mkdir -p "$NEW_CONFIG_DIR"
            mv "$user_dir"/* "$NEW_CONFIG_DIR/"
            chown -R $(basename $user_dir):$(basename $user_dir) "$NEW_CONFIG_DIR"
        fi
    done
}

migrate_config

exit 0

edit: exit 0 I think needed this time...

pghvlaans · 05-13-2024, 05:20 PM

Would information in the ChangeLog and eventually "changes and hints" not be more appropriate for the gFTP settings change? Currently, shared-mime-info is the only package that touches $HOME at all during installation, and that's just to run update-mime-database, not move directories around.