Configuration summary
2 Attachment(s)
For some packages it could be helpful to provide the configuration summary included in the configure log (in case there is one, of course).
This can help user wanting to tune the build to add or remove features, when allowed by the software. This would go in the source directory alongside the SlackBuild. Two examples are attached: one using the SlackBuild for libewp in Slackware-current another one for mlterm (SlackBuild from SBo heavily modified). Maybe something similar can be provided for cmake. |
Quote:
Unlike other XDG_* variables, XDG_RUNTIME_DIR does not have a default location. Quote:
|
Quote:
Code:
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-user' |
Quote:
This proposal might require PAM. I ran a quick test. On other distros /run/user is chmod 755, chown root:root. The user does not have permissions to create /run/user/$UID. Something else is required to create that directory with the correct permissions and ownership. |
Quote:
And my user is called 'user' (to be precise it's '/tmp/runtime-your_current_username') Quote:
|
I consider the XDG Base Directory Specification as the reference for such environment variables.
I never had (or heard of ) an issue with these settings which comply with the aforementioned specification: Code:
The reason I prefer to have the same directory for XDG_RUNTIME_DIR and XDG_CACHE_HOME is that can help software that need a socket provided by another software to find it. PS This proposal of course doesn't require PAM. |
Quote:
Quote:
Quote:
I appreciate your feedback Didier. I think you have hit upon a useful idea. And I like the idea that PID files, sockets, etc. are all in tmpfs. Edit: Regarding permissions, if /run/user is 777 then each user can create /run/user/$UID and export XDG_RUNTIME_DIR respectively. The distinction is on other distros where /run/user is 755 root:root and each $UID subdirectory is 700 $USER:$USER. I chose /run/user because that is the norm on all other users. Perhaps though, if Qt/KDE is defaulting to /tmp/runtime-$USER, my proposal would work just fine there. I will run a proof-of-concept test. |
Quote:
Code:
drwxr-xr-x root/root 0 2018-05-01 10:22 var/run/dbus/ While the idea to symlink /var/run to /run is probably good, i still fear that some packages will need adjustments to handle it. |
Quote:
This raises another Current feature request. Slackware does not have a way to create a $HOME/.xsession-errors log. I have used my own /etc/xprofile to create the log and I modify the xinitrc files to source /etc/xprofile. Pat, could we please find a way to automatically create $HOME/.xsession-errors? |
Quote:
I do not recall how I modified my Slackware systems to use /var/run. I think all I did was boot or drop to init 1, delete all /var/run files and directories, and then manually created the sym link. As I mentioned previously, for those who do not like the idea, a simple /etc/default/var_run would allow users to define the behavior they prefer. rc.S would need to be modified to clean the disk of hard-coded subdirectories after the user configures /var/run to tmpfs and reboots. Something like: Code:
if [ -r /etc/default/var_run ]; then Quote:
|
Quote:
These features are so old they have beard. Code:
grep .xprofile /etc/X11/xdm/Xsession |
I created /etc/profile.d/xdg.sh:
Code:
if [ ! -d /tmp/runtime-$USER ]; then dconf gvfs keyring pulse Normally, because XDG_RUNTIME_DIR is not defined in Slackware, the same directories are created elsewhere: dconf -> ~/.cache/dconf gvfs -> ~/.gvfs keyring -> ~/.cache/keyring-$uuid pulse -> /tmp/pulse-$uuid In a stock Slackware, XDG_CACHE_HOME also is not defined. According to the XDG Base Directory Specification, compliant apps are supposed to default to ~/.cache when not defined. Although obviously apps are working without the defined environment variables and using the variables offers no noticeable performance difference, using the variables does nicely consolidate temporary files into one location. Without the environment variables the temporary files are stored in three different locations. If /tmp is mounted using tmpfs, this provides a cleaner way of ensuring various PID and socket files are deleted on reboot. Defining $XDG_CACHE_HOME to a tmpfs location might work for some users but likely not for all. For example, some users might want to retain their browser cache across reboots without explicitly defining a cache directory in their browser profile. I hope this information helps! :) |
Quote:
|
Quote:
Code:
drwxr-xr-x root/root 0 2018-05-01 10:22 var/run/dbus/ Code:
drwxr-xr-x root/root 0 2018-05-17 12:29 var/run/samba/ Code:
drwxr-xr-x root/root 0 2018-05-11 18:45 var/run/named/ Code:
drwxr-xr-x root/root 0 2018-04-13 10:38 var/run/iptraf-ng/ Code:
drwxr-xr-x root/root 0 2018-06-12 16:35 var/run/nscd/ So sorry for the noise and one more vote from me to symlink /var/run to /run (and then removing above directories from the packages) :) |
Interesting discussion that probably should have it's own thread.
|
All times are GMT -5. The time now is 11:15 AM. |