Slackware-current 64 bit, pure-alsa, how to manage updates for pure-alsa-system?

phenixia2003 · 11-18-2018, 09:12 AM

Hello,

Quote:

Originally Posted by Didier Spaier

This already exists, as I reminded you in post #2, so no change is needed in slackpkg. Rather, you need to carefully read the man pages:
man slackpkg
man slackpkg.conf
and the file /etc/slackpg/slackpkg.conf that includes enlightening comments.

For the moment this is the solution. However, as I said some time ago, when -current will turn -stable, patches for "pure alsa" will have to be publish elswhere than in "patches".

--
SeB

perseus12 · 11-18-2018, 11:41 AM

Quote:

GazL:
I guess it would depend on whether there are ever any additional 'alternative' packages in extra/ that might replace some other stock packages. I raise it only as a possibility and something to watch out for. I'm not suggesting it will cause a problem as things stand.

My own scripts just work on directories rather than some notion of predefined "repositories", which, though primitive, allows a lot of flexibility.

I've been using this to follow current for around 5 years now. It works for me, but as I said above, not everyone wants to keep local package mirrors.

After having tried a few 'other' methods I now also use the same as you describe :-)
Actually I keep rsync repositories for 14.1, 14.2 patches and then current since I maintain a few laptops for non-tech friends

igadoter · 11-19-2018, 03:10 AM

I changed priority in slackpkg.conf. I ran today updates and slackpkg tried to update 'xf86-video-nouveau-blacklist-noarch-1.txz'. I guess no one wanted to be such thing to be done blindly. I don't remember now but this package actually blacklists nouveau driver? But I was lucky: I don't have nvidia gpu