Slackware-current 64 bit, pure-alsa, how to manage updates for pure-alsa-system?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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".
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
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
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.