Mass storage devices do not disappear from Thunar after disconnecting

You have a problem with Salix? Post here and we'll do what we can to help.
Post Reply
user_salix
Posts: 1
Joined: 11. Dec 2019, 20:15

Mass storage devices do not disappear from Thunar after disconnecting

Post by user_salix »

Hi,
problem is well described in here
https://forum.manjaro.org/t/android-pho ... ting/34347

All things, as i understoond, boils to the point that in Salix 14.2 quite big number of packages are outdated compare to present day.
For example package gvfs version is 1.26.3-x86_64-1.
The last version in Slacware64-current is gvfs-1.42.2-x86_64-1.txz

So it is just one example.

Is it possible to get more recent versions of some packages of interest in Salix 14.2 from Slackware current or Slackel?
What mirror to use in this situation and how that don't upgrade whole system but still remain
compatible and consistent with general system autoupdate or Gslapt?

how to change source file /etc/slapt-get/slapt-getrc ? One in use looks like that:

WORKINGDIR=/var/slapt-get
EXCLUDE=^aaa_elflibs,^aaa_base,^devs,^rootuser-settings,^zzz-settings.*,-i?86-
SOURCE=http://download.salixos.org/x86_64/slac ... /:OFFICIAL
SOURCE=http://download.salixos.org/x86_64/slac ... /:OFFICIAL
SOURCE=http://download.salixos.org/x86_64/14.2/:PREFERRED
SOURCE=http://download.salixos.org/x86_64/extra-14.2/:OFFICIAL
User avatar
gapan
Salix Wizard
Posts: 6238
Joined: 6. Jun 2009, 17:40

Re: Mass storage devices do not disappear from Thunar after disconnecting

Post by gapan »

user_salix wrote: 11. Dec 2019, 20:46 Is it possible to get more recent versions of some packages of interest in Salix 14.2 from Slackware current or Slackel?
It is, but you really shouldn't. Noone can predict what might break.
Image
Image
DidierSpaier
Posts: 518
Joined: 20. Jun 2016, 20:15

Re: Mass storage devices do not disappear from Thunar after disconnecting

Post by DidierSpaier »

If really you want a newer version, the best thing to do would be to download the source files for the packages from a mirror of Slackware current or Slackel then build the package yourself. This works often, but not in all cases. Caveat: be aware that in the SlackBuilds for Slackware current there is often this code snippet:

Code: Select all

# Don't package .la files:
rm -f $PKG/usr/lib${LIBDIRSUFFIX}/*.la
If it is present, remove or comment out the second line, as else already installed packages that depend on this one will probably fail. Which is one more reason not to install an upgraded package not intended for Salix but instead rebuild it yourself.
Post Reply