LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 04-17-2021, 02:41 PM   #196
stormtracknole
Senior Member
 
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,208

Rep: Reputation: 188Reputation: 188

LuckyCyborg,

Went through the steps. Pretty easy and it looks like Pipewire is working.

I had to build daemon with the following option:

Code:
./configure --enable-logind
make
make install
Also, I had to make sure to create $HOME/.run. I don't if it would have been created automatically.
 
2 members found this post helpful.
Old 04-17-2021, 02:55 PM   #197
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 1,311

Rep: Reputation: 1058Reputation: 1058Reputation: 1058Reputation: 1058Reputation: 1058Reputation: 1058Reputation: 1058Reputation: 1058
Quote:
Originally Posted by stormtracknole View Post
LuckyCyborg,

Went through the steps. Pretty easy and it looks like Pipewire is working.

I had to build daemon with the following option:

Code:
./configure --enable-logind
make
make install
Nice!

If you want to still package it, this is the way I do myself:

Code:
#!/bin/bash

# Copyright 2005-2018  Patrick J. Volkerding, Sebeka, MN, USA
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
#    notice, this list of conditions and the following disclaimer.
#
#  THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED
#  WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
#  MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO
#  EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
#  SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
#  PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
#  OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
#  WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
#  OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
#  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

cd $(dirname $0) ; CWD=$(pwd)

PKGNAM=daemon
VERSION=${VERSION:-$(echo $PKGNAM-*.tar.?z | rev | cut -f 3- -d . | cut -f 1 -d - | rev)}
BUILD=${BUILD:-1}

NUMJOBS=${NUMJOBS:-" -j$(expr $(nproc) + 1) "}

# Automatically determine the architecture we're building on:
if [ -z "$ARCH" ]; then
  case "$(uname -m)" in
    i?86) ARCH=i586 ;;
    arm*) readelf /usr/bin/file -A | egrep -q "Tag_CPU.*[4,5]" && ARCH=arm || ARCH=armv7hl ;;
    # Unless $ARCH is already set, use uname -m for all other archs:
    *) ARCH=$(uname -m) ;;
  esac
  export ARCH
fi

# If the variable PRINT_PACKAGE_NAME is set, then this script will report what
# the name of the created package would be, and then exit. This information
# could be useful to other scripts.
if [ ! -z "${PRINT_PACKAGE_NAME}" ]; then
  echo "$PKGNAM-$VERSION-$ARCH-$BUILD.txz"
  exit 0
fi

TMP=${TMP:-/tmp}
PKG=$TMP/package-$PKGNAM

if [ "$ARCH" = "i386" ]; then
  SLKCFLAGS="-O2 -march=i386 -mcpu=i686"
elif [ "$ARCH" = "i486" ]; then
  SLKCFLAGS="-O2 -march=i486 -mtune=i686"
elif [ "$ARCH" = "i586" ]; then
  SLKCFLAGS="-O2 -march=i586 -mtune=i686"
elif [ "$ARCH" = "i686" ]; then
  SLKCFLAGS="-O2 -march=i686"
elif [ "$ARCH" = "s390" ]; then
  SLKCFLAGS="-O2"
elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fPIC"
elif [ "$ARCH" = "armv7hl" ]; then
  SLKCFLAGS="-O3 -march=armv7-a -mfpu=vfpv3-d16"
else
  SLKCFLAGS="-O2"
fi

rm -rf $PKG
mkdir -p $TMP $PKG
cd $TMP
rm -rf $PKGNAM-$VERSION
tar xvf $CWD/$PKGNAM-$VERSION.tar.?z || exit 1
cd $PKGNAM-$VERSION || exit 1
chown -R root:root .
find . \
  \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
  -exec chmod 755 {} \+ -o \
  \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
  -exec chmod 644 {} \+

./configure \
  --prefix=/usr \
  --enable-logind

make $NUMJOBS CFLAGS="$SLKCFLAGS" || exit 1

make install DESTDIR=$PKG || exit 1
make install-daemon-conf DESTDIR=$PKG || exit 1
make install-daemon-html DESTDIR=$PKG DAEMON_HTMLDIR=/usr/doc/$PKGNAM-$VERSION || exit 1

mv $PKG/etc/daemon.conf $PKG/etc/daemon.conf.new

mkdir -p $PKG/usr/doc/$PKGNAM-$VERSION
cp -a \
  COPYING* INSTALL LICENSE README* REFERENCES \
  $PKG/usr/doc/$PKGNAM-$VERSION

# If there's a CHANGELOG, installing at least part of the recent history
# is useful, but don't let it get totally out of control:
if [ -r CHANGELOG ]; then
  DOCSDIR=$(echo $PKG/usr/doc/*-$VERSION)
  cat CHANGELOG | head -n 1000 > $DOCSDIR/CHANGELOG
  touch -r CHANGELOG $DOCSDIR/CHANGELOG
fi

mkdir -p $PKG/install
cat $CWD/doinst.sh > $PKG/install/doinst.sh
cat $CWD/slack-desc > $PKG/install/slack-desc

# Build the package:
cd $PKG
/sbin/makepkg -l y -c n $TMP/$PKGNAM-$VERSION-$ARCH-$BUILD.txz
Code:
#!/bin/sh
config() {
  NEW="$1"
  OLD="`dirname $NEW`/`basename $NEW .new`"
  # If there's no config file by that name, mv it over:
  if [ ! -r $OLD ]; then
    mv $NEW $OLD
  elif [ "`cat $OLD | md5sum`" = "`cat $NEW | md5sum`" ]; then # toss the redundant copy
    rm $NEW
  fi
  # Otherwise, we leave the .new copy for the admin to consider...
}

config etc/daemon.conf.new
Code:
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.


      |-----handy-ruler------------------------------------------------------|
daemon: daemon (turns other processes into daemons)
daemon:
daemon: Daemon turns other processes into daemons. There are many tasks that
daemon: need to be performed to correctly set up a daemon process. This can
daemon: be tedious. Daemon performs these tasks for other processes. This is
daemon: useful for writing daemons in languages other than C, C++ or Perl
daemon: (e.g. `/bin/sh`, Java).
daemon:
daemon: http://libslack.org/daemon/
daemon:
daemon:
In order, they are: daemon.SlackBuild, doinst.sh and slack-desc. Build initially made by @ZhaoLin1457, of course.

Quote:
Originally Posted by stormtracknole View Post
Also, I had to make sure to create $HOME/.run. I don't if it would have been created automatically.
From what I seen, on my boxes the daemon supervisor always creates alone that ~/.run directory. However if you believe that you found a bug, feel free to contact the developer. @raforg appears to be a really friendly guy.

Last edited by LuckyCyborg; 04-17-2021 at 03:13 PM.
 
4 members found this post helpful.
Old 04-17-2021, 02:57 PM   #198
stormtracknole
Senior Member
 
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,208

Rep: Reputation: 188Reputation: 188
Quote:
Originally Posted by LuckyCyborg View Post
Nice! If you want to still package it, this is the way I do myself:
Code:
#!/bin/bash

# Copyright 2005-2018  Patrick J. Volkerding, Sebeka, MN, USA
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
#    notice, this list of conditions and the following disclaimer.
#
#  THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED
#  WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
#  MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO
#  EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
#  SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
#  PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
#  OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
#  WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
#  OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
#  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

cd $(dirname $0) ; CWD=$(pwd)

PKGNAM=daemon
VERSION=${VERSION:-$(echo $PKGNAM-*.tar.?z | rev | cut -f 3- -d . | cut -f 1 -d - | rev)}
BUILD=${BUILD:-1}

NUMJOBS=${NUMJOBS:-" -j$(expr $(nproc) + 1) "}

# Automatically determine the architecture we're building on:
if [ -z "$ARCH" ]; then
  case "$(uname -m)" in
    i?86) ARCH=i586 ;;
    arm*) readelf /usr/bin/file -A | egrep -q "Tag_CPU.*[4,5]" && ARCH=arm || ARCH=armv7hl ;;
    # Unless $ARCH is already set, use uname -m for all other archs:
    *) ARCH=$(uname -m) ;;
  esac
  export ARCH
fi

# If the variable PRINT_PACKAGE_NAME is set, then this script will report what
# the name of the created package would be, and then exit. This information
# could be useful to other scripts.
if [ ! -z "${PRINT_PACKAGE_NAME}" ]; then
  echo "$PKGNAM-$VERSION-$ARCH-$BUILD.txz"
  exit 0
fi

TMP=${TMP:-/tmp}
PKG=$TMP/package-$PKGNAM

if [ "$ARCH" = "i386" ]; then
  SLKCFLAGS="-O2 -march=i386 -mcpu=i686"
elif [ "$ARCH" = "i486" ]; then
  SLKCFLAGS="-O2 -march=i486 -mtune=i686"
elif [ "$ARCH" = "i586" ]; then
  SLKCFLAGS="-O2 -march=i586 -mtune=i686"
elif [ "$ARCH" = "i686" ]; then
  SLKCFLAGS="-O2 -march=i686"
elif [ "$ARCH" = "s390" ]; then
  SLKCFLAGS="-O2"
elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fPIC"
elif [ "$ARCH" = "armv7hl" ]; then
  SLKCFLAGS="-O3 -march=armv7-a -mfpu=vfpv3-d16"
else
  SLKCFLAGS="-O2"
fi

rm -rf $PKG
mkdir -p $TMP $PKG
cd $TMP
rm -rf $PKGNAM-$VERSION
tar xvf $CWD/$PKGNAM-$VERSION.tar.?z || exit 1
cd $PKGNAM-$VERSION || exit 1
chown -R root:root .
find . \
  \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
  -exec chmod 755 {} \+ -o \
  \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
  -exec chmod 644 {} \+

./configure \
  --prefix=/usr \
  --enable-logind

make $NUMJOBS CFLAGS="$SLKCFLAGS" || exit 1

make install DESTDIR=$PKG || exit 1
make install-daemon-conf DESTDIR=$PKG || exit 1
make install-daemon-html DESTDIR=$PKG DAEMON_HTMLDIR=/usr/doc/$PKGNAM-$VERSION || exit 1

mv $PKG/etc/daemon.conf $PKG/etc/daemon.conf.new

mkdir -p $PKG/usr/doc/$PKGNAM-$VERSION
cp -a \
  COPYING* INSTALL LICENSE README* REFERENCES \
  $PKG/usr/doc/$PKGNAM-$VERSION

# If there's a CHANGELOG, installing at least part of the recent history
# is useful, but don't let it get totally out of control:
if [ -r CHANGELOG ]; then
  DOCSDIR=$(echo $PKG/usr/doc/*-$VERSION)
  cat CHANGELOG | head -n 1000 > $DOCSDIR/CHANGELOG
  touch -r CHANGELOG $DOCSDIR/CHANGELOG
fi

mkdir -p $PKG/install
cat $CWD/doinst.sh > $PKG/install/doinst.sh
cat $CWD/slack-desc > $PKG/install/slack-desc

# Build the package:
cd $PKG
/sbin/makepkg -l y -c n $TMP/$PKGNAM-$VERSION-$ARCH-$BUILD.txz
Code:
#!/bin/sh
config() {
  NEW="$1"
  OLD="`dirname $NEW`/`basename $NEW .new`"
  # If there's no config file by that name, mv it over:
  if [ ! -r $OLD ]; then
    mv $NEW $OLD
  elif [ "`cat $OLD | md5sum`" = "`cat $NEW | md5sum`" ]; then # toss the redundant copy
    rm $NEW
  fi
  # Otherwise, we leave the .new copy for the admin to consider...
}

config etc/daemon.conf.new
Code:
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.


      |-----handy-ruler------------------------------------------------------|
daemon: daemon (turns other processes into daemons)
daemon:
daemon: Daemon turns other processes into daemons. There are many tasks that
daemon: need to be performed to correctly set up a daemon process. This can
daemon: be tedious. Daemon performs these tasks for other processes. This is
daemon: useful for writing daemons in languages other than C, C++ or Perl
daemon: (e.g. `/bin/sh`, Java).
daemon:
daemon: http://libslack.org/daemon/
daemon:
daemon:
In order, they are: daemon.SlackBuild, doinst.sh and slack-desc. Build initially made by @ZhaoLin1457, of course.



From what I seen, on my boxes the daemon supervisor always creates alone that ~/.run directory. However if you believe that you found a bug, feel free to contact the developer. @raforg appears a really friendly guy.
Awesome! Thanks for the SlackBuild. My mistake was to create the .run directory before I let the daemon service handle it.
 
2 members found this post helpful.
Old 04-17-2021, 03:21 PM   #199
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 1,311

Rep: Reputation: 1058Reputation: 1058Reputation: 1058Reputation: 1058Reputation: 1058Reputation: 1058Reputation: 1058Reputation: 1058
Quote:
Originally Posted by stormtracknole View Post
Awesome! Thanks for the SlackBuild. My mistake was to create the .run directory before I let the daemon service handle it.
It truly is!

What the @ZhaoLin1457 did with this little daemon supervisor is truly a Haiku on practical engineering of emulating systemd's user target.

I tried myself too - BUT my take was embarrassing complicated and unpractical, compared with his one:

a system of having rc.d like scripts on /etc/user.d which are started by a master script run by the XDG autostart and another script watching the elogind on DBUS for user logout.

Last edited by LuckyCyborg; 04-17-2021 at 04:00 PM.
 
3 members found this post helpful.
Old 04-17-2021, 04:19 PM   #200
stormtracknole
Senior Member
 
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,208

Rep: Reputation: 188Reputation: 188
My kudos to @ZhaoLin1457!!
 
2 members found this post helpful.
Old 04-17-2021, 04:28 PM   #201
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,141

Rep: Reputation: 5678Reputation: 5678Reputation: 5678Reputation: 5678Reputation: 5678Reputation: 5678Reputation: 5678Reputation: 5678Reputation: 5678Reputation: 5678Reputation: 5678
Quote:
Originally Posted by LuckyCyborg View Post
I seriously doubt that any of those proposed changes have any effect on the X11 sessions of Plasma5 or whatever other desktop environment.
Ok, so your belief that everything works fine and whatever testing you've done should surpass any testing that Pat should do on his end?

Just think about it... how long has Eric and many others felt that ktown was ready for -current? And how long did it take Pat to get it in there? Even if he was waiting for PAM to be brought in, it still took 6 months after PAM was incorporated into the main tree before vtown even arrived... and another month for vtown to replace KDE4 in the main tree.
 
Old 04-17-2021, 05:14 PM   #202
Jan K.
Member
 
Registered: Apr 2019
Location: Esbjerg
Distribution: slackware...
Posts: 247

Rep: Reputation: 170Reputation: 170
Quote:
Originally Posted by LuckyCyborg View Post
It truly is!

What the @ZhaoLin1457 did with this little daemon supervisor is truly a Haiku on practical engineering of emulating systemd's user target.

I tried myself too - BUT my take was embarrassing complicated and unpractical, compared with his one:

a system of having rc.d like scripts on /etc/user.d which are started by a master script run by the XDG autostart and another script watching the elogind on DBUS for user logout.
May I suggest a dedicated thread "Tuning pipewire, plasma, wayland and Slackware" or something?

Could make testing/reporting easier to follow and I would love to see both your findings in one place. It's a bit scattered both in this thread and elsewhere...

Thank you both for your dedication and beautiful work. Amazing times ahead!
 
2 members found this post helpful.
Old 04-17-2021, 07:35 PM   #203
PROBLEMCHYLD
Senior Member
 
Registered: Apr 2015
Posts: 1,156

Rep: Reputation: Disabled
Quote:
Originally Posted by Jan K. View Post
May I suggest a dedicated thread "Tuning pipewire, plasma, wayland and Slackware" or something?

Could make testing/reporting easier to follow and I would love to see both your findings in one place. It's a bit scattered both in this thread and elsewhere...

Thank you both for your dedication and beautiful work. Amazing times ahead!
Me too. Sh!+ is scattered all over the place like broken glass.
 
Old 04-18-2021, 04:02 AM   #204
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 1,311

Rep: Reputation: 1058Reputation: 1058Reputation: 1058Reputation: 1058Reputation: 1058Reputation: 1058Reputation: 1058Reputation: 1058
Quote:
Originally Posted by bassmadrigal View Post
Ok, so your belief that everything works fine and whatever testing you've done should surpass any testing that Pat should do on his end?
This "whatever testing" I did is what I have can do on my eleven "good for trash" boxes. And yeah, I believe that's enough, because I talk about some ultra-verified bugfixes, NOT be adopting another desktop environment.

IF you believe that I am wrong, feel free to install Slackware-current on your ThreadRipper powered box with WTF!? amount of memory and OMG!? storage space on those NVME of yours - or at least grab a second hand computer worth of 20 dollars or so. Then to test what I did.

Until you bother to do this, leaving the convenient place of Slackware 14.2 and daring to challenge Siberia on Winter Slackware-current, please trust my work and my limited testing. At least be kind to contradict me with engineering arguments, NOT with ideologically ones.

As someone who literally got a solid Soviet education, trust me that I am well trained to resist at ideological arguments. Specially when your main argument is: "Our Dear Leader said so!"

BTW, as you can see in the attached screenshot, I can show you yet another box running happily on Wayland/Plasma5.

Ask yourself: how the heck it always works for me, even on that damn old min-PC with C2D processor at 2,26GHz, 4GB DDR2 667MHz memories and an OpenGL 2.0 capable graphics integrated on motherboard, BUT almost everybody else get a glorious crash on starting that Wayland/Plasma5 of Slackware?

Maybe because I have applied a series of bugfixes, which are in the fact those changes proposed by me?

Quote:
Originally Posted by bassmadrigal View Post
Just think about it... how long has Eric and many others felt that ktown was ready for -current? And how long did it take Pat to get it in there? Even if he was waiting for PAM to be brought in, it still took 6 months after PAM was incorporated into the main tree before vtown even arrived... and another month for vtown to replace KDE4 in the main tree.
Honestly, I believe also that the Plasma5 was ready since 3 years ago. At least 3 years if not more.

But very probably our BDFL awaited for a Marvel: the ConsoleKit2 to be fully adopted by that KDE software. Which does not happened, as many long awaited marvels.

So, that "how long did it take Pat to get it in there" was just for political reasons.
Attached Thumbnails
Click image for larger version

Name:	Screenshot_20210418_110930.jpg
Views:	76
Size:	165.4 KB
ID:	36152  

Last edited by LuckyCyborg; 04-18-2021 at 05:06 AM.
 
4 members found this post helpful.
Old 04-18-2021, 05:14 AM   #205
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,480

Rep: Reputation: 7792Reputation: 7792Reputation: 7792Reputation: 7792Reputation: 7792Reputation: 7792Reputation: 7792Reputation: 7792Reputation: 7792Reputation: 7792Reputation: 7792
Quote:
Originally Posted by Jan K. View Post
May I suggest a dedicated thread "Tuning pipewire, plasma, wayland and Slackware" or something?

Could make testing/reporting easier to follow and I would love to see both your findings in one place. It's a bit scattered both in this thread and elsewhere...

Thank you both for your dedication and beautiful work. Amazing times ahead!
I am still hoping for one or more articles on docs.slackware.com that properly document configuration and usage of pipewire in Slackware.
The LQ forum is nice for discussions but it is not the correct place to provide documentation and procedures.
 
8 members found this post helpful.
Old 04-18-2021, 08:00 AM   #206
nobodino
Member
 
Registered: Jul 2010
Location: in France
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint,Manjaro...
Posts: 865

Rep: Reputation: 459Reputation: 459Reputation: 459Reputation: 459Reputation: 459
Another piece of advice from a humble contributor:
- create a github project page or gitlab, and put your new packages on.
- Make publicity on LQ.

Trying to push by force whatever the quality of your project won't accelerate its acceptance.
Look at the time it took Alien Bob to make Plasma accepted in Slackware.

You may say Slackware is too conservative from your point of view, but whining won't change anything to that.

Good luck to you.
 
3 members found this post helpful.
Old 04-18-2021, 02:32 PM   #207
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,141

Rep: Reputation: 5678Reputation: 5678Reputation: 5678Reputation: 5678Reputation: 5678Reputation: 5678Reputation: 5678Reputation: 5678Reputation: 5678Reputation: 5678Reputation: 5678
Quote:
Originally Posted by LuckyCyborg View Post
IF you believe that I am wrong, feel free to install Slackware-current on your ThreadRipper powered box with WTF!? amount of memory and OMG!? storage space on those NVME of yours - or at least grab a second hand computer worth of 20 dollars or so. Then to test what I did.
I am not using a threadripper, instead an almost 4 year old Ryzen 7. I also only have 1TB of storage on my NVMe drive and 70TB of storage across 8 platter hard drives that I've collected over many years. However, system specs have nothing to do with my argument, so please don't try and bring up something that doesn't apply. That is considered an ad hominem attack (attacking the person rather than the argument).

Quote:
Originally Posted by LuckyCyborg View Post
This "whatever testing" I did is what I have can do on my eleven "good for trash" boxes. And yeah, I believe that's enough, because I talk about some ultra-verified bugfixes, NOT be adopting another desktop environment.

Until you bother to do this, leaving the convenient place of Slackware 14.2 and daring to challenge Siberia on Winter Slackware-current, please trust my work and my limited testing. At least be kind to contradict me with engineering arguments, NOT with ideologically ones.
Again, the version of Slackware that I'm running has no bearing on the situation. You seem to have a lot of time on your hands that allows you to manage so many boxes and do a large amount of testing. I'm jealous. I barely have time to stay up on the forum (and some days I can't even manage that). I don't have the time available right now to maintain a -current install. I wish I did... I love doing that type of testing, but my life just doesn't currently allow for it. But, again, the version of Slackware that I'm running has nothing to do with speculating on the reasons why your fixes have not been added to Slackware.

I'm not stating that what you have proposed is not ready for primetime, instead I'm stating that Pat may believe it's not ready for primetime and feels he needs to do a large amount of testing before he is ready to incorporate it into the main tree. Since he is the BDFL, his say is the only say that matters.

Quote:
Originally Posted by LuckyCyborg View Post
As someone who literally got a solid Soviet education, trust me that I am well trained to resist at ideological arguments. Specially when your main argument is: "Our Dear Leader said so!"
If you're so well trained to "resist idealogical arguments", can you also stay away from ad hominem attacks? My hardware specs and version of Slackware have nothing to do with whether Pat believes your changes are ready for the main tree.

Quote:
Originally Posted by LuckyCyborg View Post
Ask yourself: how the heck it always works for me, even on that damn old min-PC with C2D processor at 2,26GHz, 4GB DDR2 667MHz memories and an OpenGL 2.0 capable graphics integrated on motherboard, BUT almost everybody else get a glorious crash on starting that Wayland/Plasma5 of Slackware?

Maybe because I have applied a series of bugfixes, which are in the fact those changes proposed by me?
That isn't the question. The question is does Pat feel your fixes can only lead to good things or could there be the possibility of unknown side-effects? If he believes the latter, the only way to determine that is to test and verify they don't exist.

Quote:
Originally Posted by LuckyCyborg View Post
Honestly, I believe also that the Plasma5 was ready since 3 years ago. At least 3 years if not more.
Which goes to show my point even more... even if you feel it is ready, Pat may not. If you convince every single person in the world other than Pat that it's ready, guess what? It still won't be added.

Quote:
Originally Posted by LuckyCyborg View Post
But very probably our BDFL awaited for a Marvel: the ConsoleKit2 to be fully adopted by that KDE software. Which does not happened, as many long awaited marvels.
But Plasma5 was working with ConsoleKit2 for a LONG time before Eric switched over to elogind. Yes, 3rd-party software may not work properly (skype), but when has that stopped Pat from pushing forward? How many times has Pat pushed a newer kernel or Xorg into -current that wasn't supported by Nvidia drivers yet? Enough that I've certainly lost count...

Quote:
Originally Posted by LuckyCyborg View Post
So, that "how long did it take Pat to get it in there" was just for political reasons.
That your guess, just like it's my guess that the reason your changes haven't been incorporated yet is because Pat wants to test it more.
 
Old 04-18-2021, 02:46 PM   #208
Tonus
Member
 
Registered: Jan 2007
Location: Paris, France
Distribution: Slackware-current
Posts: 912
Blog Entries: 3

Rep: Reputation: 248Reputation: 248Reputation: 248
I have to admit that having tailored something like that may grow LuckyCyborg and ZhaoLin impatient in a (general ?) Slacker point of view...
Always hard to wait, especially with no input of how things are considered...

Sure I wish I had more time to extensive test that and eventually provide some repo and slackware oriented documentation to help...

If it's still the time I hope I will do in mid may....
 
1 members found this post helpful.
Old 04-19-2021, 07:51 PM   #209
drgibbon
Senior Member
 
Registered: Nov 2014
Distribution: Slackware64 -current
Posts: 1,040

Rep: Reputation: 711Reputation: 711Reputation: 711Reputation: 711Reputation: 711Reputation: 711Reputation: 711
Daemon added to -current, so you guys can stop arguing about it now
Code:
kde/plasma-workspace-5.21.4-x86_64-2.txz: Rebuilt.
       Patched to fix missing GTK+ window decorations and config file reading
       in a wayland session.
       Added "Full Wayland" session type (less stable / more experimental).
       The standard Plasma Wayland session will allow apps to use XCB rather
       than native Wayland, which is currently more stable.
       Thanks to LuckyCyborg.
[...]
n/daemon-0.8-x86_64-1.txz: Added.
       Thanks to ZhaoLin1457 and LuckyCyborg.

Last edited by drgibbon; 04-19-2021 at 08:01 PM.
 
7 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Firefox 3 beta 4 code freeze tonight, beta 5 release looks likely LXer Syndicated Linux News 0 02-28-2008 11:20 AM
LXer: This week at LWN: GPLv3 beta 2 and LGPLv3 beta 1 LXer Syndicated Linux News 0 08-05-2006 01:54 AM
LXer: Mozilla Firefox 2.0 Beta 1 Release Candidate Builds Available, Final Beta 1 Set for Later This Week LXer Syndicated Linux News 0 07-13-2006 02:54 AM
Vista beta vs. "Linux beta" Furlinastis General 5 05-30-2006 09:02 AM
Beta testing Beta 8 -- Boot Loader screws up 1kyle SUSE / openSUSE 0 03-27-2006 03:36 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:21 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration