LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
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-25-2020, 04:29 PM   #1
Skaendo
Senior Member
 
Registered: Dec 2014
Location: West Texas, USA
Distribution: Slackware64-14.2
Posts: 1,445

Rep: Reputation: Disabled
LXQt 0.15.0 for Slackware64-current


Anyone that would like to test out the LXQt 0.15.0 desktop environment on -current, here it is in all it's glory.

https://gitlab.com/slackdesk/lxqt

These are not compiled binaries, only SlackBuilds!

The build time for me on a C2D @ 2GHz w/ 4GB 800MHz RAM @ -j4 is a little over an hour, and comes to about 45MB.

Sorry that I do not have a "build order", I generally build in (and recommend) slackrepo. I'd be more than happy to help with a slackrepo config file if needed. Or if someone was to figure out the order, I would be more than happy to include it.


## A couple of notes ##

I have not tested this on 32bit Slackware, use at your own risk!

Please use the supplied openbox for the window manager, you will still need to select xinitrc.lxqt via xwmconfig. This makes LXQt completely standalone and no other DE's (XFCE) need to be installed in order for LXQt to function properly.

extra/pavucontrol-qt: This is an "official" LXQt package, but as it was tested it was found that it is just duplicating the stock Slackware pavucontrol. If you would rather run LXQt's Qt version, you should consider removing the Slackware package or else you'll have duplicates. Please note that removing the Slackware pavucontrol package and using only the LXQt pavucontrol-qt package has not been tested.

extra/screengrab: This is another "official" LXQt package that when installed is a duplicate application since lximage-qt has it's own screenshot application.

testing/organizer: This is not working at the moment.
 
Old 04-25-2020, 06:01 PM   #2
giomat
Member
 
Registered: Jul 2017
Posts: 342

Rep: Reputation: 243Reputation: 243Reputation: 243
thanks for making these, i used them to build the 0.14 version with my own hacked together build script.
i was never able to properly use slackrepo with your slackbuilds, it could be nice if you post your config or some instructions
 
2 members found this post helpful.
Old 04-25-2020, 06:15 PM   #3
Skaendo
Senior Member
 
Registered: Dec 2014
Location: West Texas, USA
Distribution: Slackware64-14.2
Posts: 1,445

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by giomat View Post
thanks for making these, i used them to build the 0.14 version with my own hacked together build script.
i was never able to properly use slackrepo with your slackbuilds, it could be nice if you post your config or some instructions
Here is a really generic config, it should work as-is for a default slackrepo install (save as /etc/slackrepo/slackrepo_lxqt.conf):
Code:
# This is the slackrepo configuration file for Skaendo's LXQt repository.
#
# The priority order for configuration is:
# (1) Environment variables when slackrepo is called
# (2) ~/.genreprc   [for gen_repos_files.sh only]
# (3) ~/.slackreporc
# (4) /etc/slackrepo/slackrepo_lxqt.conf
#
# %REPO% and %ARCH% will be replaced by the repo ID, Slackware version and arch

#-------------------------------------------------------------------------------
# Filestore locations

# Where is the local SlackBuild repo:
SBREPO="/var/lib/slackrepo/%REPO%/slackbuilds"

# Where to store cached sources (you will need plenty of space):
SRCREPO="/var/lib/slackrepo/%REPO%/source"

# Where to store built packages (you will need plenty of space):
PKGREPO="/var/lib/slackrepo/%REPO%/packages/current/%ARCH%"

# Where to keep backups (delete or comment this if you do not want backups):
PKGBACKUP="/var/lib/slackrepo/%REPO%/backups/current/%ARCH%"

# Where to find hintfiles for this repo:
HINTDIR="/etc/slackrepo/%REPO%/hintfiles"

# Default hintfiles are provided by the 'slackrepo-hints' package,
# which is recommended, but optional.
DEFAULT_HINTDIR="/etc/slackrepo/%REPO%/default_hintfiles/current"

# Where to store log files:
LOGDIR="/var/log/slackrepo/%REPO%"

# Where to keep the database:
DATABASE="/var/lib/slackrepo/%REPO%/database_%REPO%_%ARCH%.sqlite3"

# If you want to run slackrepo as an ordinary user, you can remove or comment
# all the above definitions, and use something like this instead, and save it
# to .slackreporc in your ordinary user's home directory:
#
#   #  Note: if you use ~ you should NOT use quotes "..."
#
#   SBREPO=~/slackrepo/%REPO%/slackbuilds
#   SRCREPO=~/slackrepo/%REPO%/source
#   PKGREPO=~/slackrepo/%REPO%/packages/current/%ARCH%
#   PKGBACKUP=~/slackrepo/%REPO%/backups/current/%ARCH%
#   HINTDIR=~/slackrepo/%REPO%/hintfiles
#   LOGDIR=~/slackrepo/%REPO%/logs
#   DATABASE=~/slackrepo/%REPO%/database_%REPO%_%ARCH%.sqlite3
#   #  You will probably want to use the default hintfiles in /etc:
#   DEFAULT_HINTDIR=/etc/slackrepo/%REPO%/default_hintfiles/current

# Where to store temporary files (you will need plenty of space):
TMP="/tmp/%REPO%"

#-------------------------------------------------------------------------------
# Package substitutions
#
# SUBSTITUTE is a space separated list of dependency substitutions.
# Note, this probably isn't useful in the lxqt repository.

SUBSTITUTE=""

#-------------------------------------------------------------------------------
# Build control variables

# Number of make jobs to set in MAKEFLAGS:
# specify it as (for example) NUMJOBS='-j3'
# to add a load average limit, specify it as (for example) NUMJOBS='-j6 -l4.5'
# or leave it blank to have this automatically determined:
#   -j$(( $(nproc) * 2 )) -l$(( $(nproc) + 1 ))"
NUMJOBS=''

# Arch for building.
# Leave blank to have this automatically determined by the build host:
ARCH=''

# Tag for built packages.
TAG='_%REPO%'

# Package compression type.
# Valid values are: tgz, txz, tbz, tlz
PKGTYPE='txz'

#-------------------------------------------------------------------------------
# Defaults for slackrepo control arguments.
# For more details see 'man slackrepo'.

VERBOSE='n'
VERY_VERBOSE='n'
DRY_RUN='n'
INSTALL='n'
CHROOT='/'
LINT='n'
KEEP_TMP='n'
COLOR='auto'
NICE='5'
NOWARNING=''

#-------------------------------------------------------------------------------
# Start and finish hooks
# you can add your own hooks and/or replace the existing hooks

HOOK_START=( gitfetch_hook )
HOOK_FINISH=( genrepos_hook )

#-------------------------------------------------------------------------------
# Variables for calling gen_repos_files.sh

# Change this to '1' if you want to enable gen_repos_files.sh
# If enabled, you *must* set correct values for all the variables below!
USE_GENREPOS='0'

# Don't change this! it is needed so gen_repos_files.sh can find your packages
REPOSROOT="$PKGREPO"

# Repository maintainer
REPOSOWNER="Local administrator <root@localhost>"

# The GPG key for the repository owner can contain a different string than
# the value of $REPOSOWNER . If you leave $REPOSOWNERGPG empty, the script will
# use the value you've set for $REPOSOWNER instead to search the GPG keyfile.
REPOSOWNERGPG=""

# Under what URL is the repository accessible:
# (this is just an example, you will need to setup the http server)
DL_URL="http://localhost/pkgrepo/%REPO%/current/%ARCH%"

# The title of the generated RSS feed:
RSS_TITLE="Local SlackBuild Packages"

# The logo picture used for the RSS feed:
RSS_ICON="http://www.slackware.com/~alien/graphics/blueorb.png"

# The URL linked to when clicking on the logo:
RSS_LINK="${DL_URL}/ChangeLog.txt"

# URL to the full changelog.txt:
RSS_CLURL="${DL_URL}/ChangeLog.txt"

# The descriptive text for the RSS feed:
RSS_DESCRIPTION="Local SlackBuild Packages"

# Maximum number of RSS feed entries to display:
RSS_FEEDMAX=15

# The RSS generator must use a unique feed identifier.
# Generate one for your feed by using the string returned by "uuidgen -t":
RSS_UUID=""

# Either use gpg or gpg2:
GPGBIN="/usr/bin/gpg"

# Optionally use gpg-agent to cache the gpg passphrase instead of letting the
# script keep it in the environment (note that if you define USE_GPGAGENT=1
# but gpg-agent is not running, you will get prompted for a passphrase every
# single time gpg runs):
USE_GPGAGENT="0"

# Generate slack-requires, slack-suggests, and slack-conflicts lines in the
# metadata files by setting FOR_SLAPTGET to "1" -- these are used by slapt-get
FOR_SLAPTGET="0"

# Follow symlinks in case the repository has symlinks like 14.0 -> 13.37
# indicating that one package works for those two Slackware releases.
# If the script does _not_ follow symlinks, then the symlinks will appear in
# the repository listing instead of the packages they point to.
FOLLOW_SYMLINKS="1"

# If the repository has separate package subdirectories then define them here.
# Separate FILELIST.TXT, MANIFEST etc.. files will be created for all of them.
REPO_SUBDIRS=""

# If you want to exclude certain directories or files from being included
# in the repository metadata, define them here (space-separated).
# Example: REPO_EXCLUDES="RCS logs .genreprc"
# .revision files were created by a previous release of slackrepo:
REPO_EXCLUDES=".revision"

#-------------------------------------------------------------------------------
# Variables for creating the SlackBuild repository if it does not already exist

# URL of the remote git repo to be cloned:
INIT_GITCLONE='https://gitlab.com/slackdesk/lxqt.git'

# Git branch to set up: current is for Slackware current, etc
INIT_GITBRANCH='current'

#-------------------------------------------------------------------------------
# Interesting environment variables you can set :-)

# Use multithreaded xz compression (decompression is still single threaded)
export XZ_OPT="--threads=0"

# Use clang instead of gcc
# (doesn't work with all packages)
# export CC=clang
# export CXX=clang++

# Use distcc
# (requires additional setup, doesn't work with all packages)
# export DISTCC_HOSTS="otherhost localhost"

# Customise slackrepo's colour palette (similar to LS_COLORS and GCC_COLORS)
# export SLACKREPO_COLORS="error=01;31:warning=01;35:success=01;32:important=01:normal=00:info=22;36:ok=00:build=22;32:skip=22;35:fail=22;31:updated=22;36"
Then build with:
Code:
slackrepo --repo=lxqt build

Last edited by Skaendo; 04-25-2020 at 06:16 PM.
 
2 members found this post helpful.
Old 04-25-2020, 06:25 PM   #4
Skaendo
Senior Member
 
Registered: Dec 2014
Location: West Texas, USA
Distribution: Slackware64-14.2
Posts: 1,445

Original Poster
Rep: Reputation: Disabled
A couple of screenshots, I left the Plasma theme by default. I don't know why, I'll probably switch it to "System" and switch it to the default wallpaper as well.
Attached Thumbnails
Click image for larger version

Name:	screenshot.jpg
Views:	130
Size:	41.0 KB
ID:	33083   Click image for larger version

Name:	screenshot-2.jpg
Views:	182
Size:	85.9 KB
ID:	33084  
 
2 members found this post helpful.
Old 04-30-2020, 12:00 PM   #5
Qury
Member
 
Registered: Feb 2004
Location: Naas,IE
Distribution: Slackware
Posts: 212

Rep: Reputation: 184Reputation: 184
@Skaendo
Thanks for the SlackBuilds

Here is my hacked build script based on the build order from the lxqt project + .info files.
Code:
#!/bin/sh

git clone https://gitlab.com/slackdesk/lxqt.git
cd $PWD/lxqt

MAKEFLAGS="-j$(expr $(nproc) + 1) "

ln -sf  $PWD/extra/pavucontrol-qt $PWD/core/

DEPS="\
muparser \
openbox \
libdbusmenu-qt5 \
polkit-qt5 \
extra-cmake-modules \
solid \
libstatgrab \
libfm-extra \
breeze-icons \
kidletime \
kwayland \
libkscreen \
kwindowsystem \
lxmenu-data \
menu-cache \
libfm \
sddm "

cd  deps 

for d in $DEPS
do
	cd "$d"
    . ./$d.info
    wget $DOWNLOAD
	( chmod +x $d.SlackBuild && env MAKEFLAGS=$MAKEFLAGS ./$d.SlackBuild && upgradepkg --install-new /tmp/$d*.t?z) || exit 1
	cd ..
done

cd ../core

CMAKE_REPOS=" \
	lxqt-build-tools \
	libqtxdg \
	liblxqt \
	libsysstat \
	libfm-qt \
	lxqt-themes \
	pavucontrol-qt \
	lxqt-about \
	lxqt-admin \
	lxqt-config \
	lxqt-globalkeys \
	lxqt-notificationd \
	lxqt-openssh-askpass \
	lxqt-policykit \
	lxqt-powermanagement \
	lxqt-qtplugin \
	lxqt-session \
	lxqt-sudo \
	pcmanfm-qt \
	lxqt-panel \
	lxqt-runner \
	lxqt-archiver \
    obconf-qt \
	lximage-qt \
	qtermwidget \
	qterminal \
    qps \
    "

for d in $CMAKE_REPOS
do
	cd "$d"
    . ./$d.info
    wget $DOWNLOAD
	( chmod +x $d.SlackBuild && env MAKEFLAGS="$MAKEFLAGS" ./$d.SlackBuild && upgradepkg --install-new /tmp/$d*.t?z) || exit 1
	cd ..
done

cd ../extra

OPTIONAL_CMAKE_REPOS=" \
	screengrab"

for d in $OPTIIONAL_CMAKE_REPOS
do
	cd "$d"
    . ./$d.info
    wget $DOWNLOAD
	( chmod +x $d.SlackBuild && env MAKEFLAGS=$MAKEFLAGS ./$d.SlackBuild && upgradepkg --install-new /tmp/$d*.t?z) || exit 1
	cd ..
done

Last edited by Qury; 04-30-2020 at 12:04 PM.
 
2 members found this post helpful.
Old 04-30-2020, 03:53 PM   #6
Skaendo
Senior Member
 
Registered: Dec 2014
Location: West Texas, USA
Distribution: Slackware64-14.2
Posts: 1,445

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Qury View Post
Here is my hacked build script based on the build order from the lxqt project + .info files.
Thanks tons for this!

I will add it to the repo along with a generic "BUILD_ORDER".
 
Old 03-22-2021, 09:28 PM   #7
Lockywolf
Member
 
Registered: Jul 2007
Posts: 683

Rep: Reputation: 253Reputation: 253Reputation: 253
Question

How is this project going on? I saw updates in the repo two months ago, but it seems to rely upon its own kde components, rather than now-stock Slackware's kde-5.

Are there any plans on submitting these slackbuilds to SBo?
 
Old 03-23-2021, 10:43 AM   #8
Skaendo
Senior Member
 
Registered: Dec 2014
Location: West Texas, USA
Distribution: Slackware64-14.2
Posts: 1,445

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Lockywolf View Post
How is this project going on? I saw updates in the repo two months ago, but it seems to rely upon its own kde components, rather than now-stock Slackware's kde-5.

Are there any plans on submitting these slackbuilds to SBo?
I have not yet decided how I want to move forward with LXQt. I would like to keep it standalone so that I can build it on Slackware without having to have KDE installed.

I suppose that I could add a bit to the readme that notes if you have KDE installed, you don't need to build the KDE components.
 
Old 03-23-2021, 02:15 PM   #9
tadgy
Member
 
Registered: May 2018
Location: UK
Distribution: Slackware (servers), Void (desktop/laptop)
Posts: 306

Rep: Reputation: 417Reputation: 417Reputation: 417Reputation: 417Reputation: 417
If you decide to provide pre-built packages (I know you said you won't, but just in case things change) I'll be happy to host them on https://slackware.uk/ so the community can take advantage of your work
 
2 members found this post helpful.
Old 03-23-2021, 03:57 PM   #10
Skaendo
Senior Member
 
Registered: Dec 2014
Location: West Texas, USA
Distribution: Slackware64-14.2
Posts: 1,445

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by tadgy View Post
If you decide to provide pre-built packages (I know you said you won't, but just in case things change) I'll be happy to host them on https://slackware.uk/ so the community can take advantage of your work
Thanks, I really appreciate that. I had thought about it before, but I barely have time to maintain the scripts. I have a central repo that is kept up to date, just not down to the DE's. Perhaps if I could re-imagine my "work flow" for them I would consider it again. I am going to try and update everything by this weekend. Thanks again.
 
2 members found this post helpful.
Old 03-25-2021, 09:14 PM   #11
Skaendo
Senior Member
 
Registered: Dec 2014
Location: West Texas, USA
Distribution: Slackware64-14.2
Posts: 1,445

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Lockywolf View Post
How is this project going on? I saw updates in the repo two months ago, but it seems to rely upon its own kde components, rather than now-stock Slackware's kde-5.

Are there any plans on submitting these slackbuilds to SBo?
OK, I think that I like where it's at right now. I have a few little details to work out still (TODO Added), like update the build script. Nothing that will affect the environment.

All the SlackBuilds are up to date, KDE packages up to 5.80.0 and libfm had a point release.

I separated the KDE dependencies so if KDE is already installed those don't need to be built.

So, kick the tires and take it for a spin. Working good here.

Last edited by Skaendo; 03-25-2021 at 09:16 PM.
 
2 members found this post helpful.
Old 03-27-2021, 12:51 PM   #12
kermitdafrog8
Member
 
Registered: Dec 2018
Location: Orlando, FL
Distribution: Slackware AARCH64 and X86_64
Posts: 340

Rep: Reputation: Disabled
LXQt 0.15.0 for Slackware64-current

When I run the build_lxqt.sh script just after openbox is installed it errors saying extra-cmake-modules no such file or directory.
 
Old 03-27-2021, 07:53 PM   #13
Skaendo
Senior Member
 
Registered: Dec 2014
Location: West Texas, USA
Distribution: Slackware64-14.2
Posts: 1,445

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by kermitdafrog8 View Post
When I run the build_lxqt.sh script just after openbox is installed it errors saying extra-cmake-modules no such file or directory.
Yea, sorry about that.

If you are building with KDE 5 installed you don't need the /deps-kde packages.

So you can do two things, remove the KDE packages from the script or place all the /deps-kde SlackBuilds in the /deps directory.

I need a little time to work on that script.
 
1 members found this post helpful.
Old 03-28-2021, 01:57 PM   #14
Skaendo
Senior Member
 
Registered: Dec 2014
Location: West Texas, USA
Distribution: Slackware64-14.2
Posts: 1,445

Original Poster
Rep: Reputation: Disabled
Ok, build script updated, one option added: "KDE=yes ./build_lxqt.sh" will build the KDE packages if you do not have KDE installed.

Only thing left is to fine tune the KDE scripts. I'll probably do that during this week.
 
1 members found this post helpful.
Old 03-29-2021, 08:43 AM   #15
FTIO
Member
 
Registered: Mar 2015
Location: Las Vegas, NV
Distribution: Slackware 15.0 x64, Slackware Live 15.0 x64
Posts: 618

Rep: Reputation: 361Reputation: 361Reputation: 361Reputation: 361
I'll try to let you know if this works in the Slackware 'Live' version of current. I can't be certain when I'll do it because at the moment I have a severely painful toothache and I've been trying to use my pain meds for my disability with my back to ease the toothache pain some...trying to get to 'Better Living Through Pharmaceuticals!'...so I hope I'm making sense here. bleh.
 
  


Reply



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
Building latest LXQt 0.14 in Slackware64-current giomat Slackware 16 06-01-2019 04:12 AM
LXer: LXQt 0.14 Desktop Adds Split View in File Manager, LXQt 1.0 Still in Development LXer Syndicated Linux News 0 01-27-2019 12:32 PM
Brightness function keys not working on Slackware64 & Slackware64 current Andersen Slackware 7 01-15-2018 04:27 AM
upgrading slackware64 13.1 multilib to slackware64 -current multilib Cultist Slackware 4 03-12-2011 09:04 AM
Updating from Slackware64-current to Slackware64 13. glore2002 Slackware 4 08-28-2009 06:50 PM

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

All times are GMT -5. The time now is 08:09 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