LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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 05-19-2018, 06:51 PM   #31
AlexSlack
Member
 
Registered: Jul 2012
Location: El Salvador
Distribution: Slackware-current
Posts: 53

Rep: Reputation: 42
Pure alsa and slackpkg+


For the ones using Slackpkg+ I use the following configuration so I don't have to worry for an unwanted update:

Code:
MIRRORPLUS['restricted']=http://slackware.org.uk/people/alien/restricted_sbrepos/current/x86_64/
MIRRORPLUS['alienbob']=http://taper.alienbase.nl/mirrors/people/alien/sbrepos/current/x86_64/

PKGS_PRIORITY=( extra:.*_alsa patches:.* slackware64:.* restricted alienbob )

REPOPLUS=( slackpkgplus restricted alienbob )
Note: It is not neccessary to add a blacklist or greylist.
 
4 members found this post helpful.
Old 05-27-2018, 05:21 AM   #32
Philip Lacroix
Member
 
Registered: Jun 2012
Distribution: Slackware
Posts: 441

Rep: Reputation: 574Reputation: 574Reputation: 574Reputation: 574Reputation: 574Reputation: 574
My hat's off to Pat: thanks for providing the choice! Everything has been working smoothly here since switching to pure Alsa. I'll be fine with whatever patching (Patching?) solution will eventually be adopted for extra/.
 
Old 05-27-2018, 08:10 AM   #33
GazL
LQ Veteran
 
Registered: May 2008
Posts: 6,873

Rep: Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982
re: patching

Has updating in-place ever been considered for Slackware? i.e. instead of a patches/ directory updated packages replace older ones in the main-package tree?

OpenBSD follow that model with a release (which is a fixed point in time), stable (which gets overwritten with important/security updates) and current (development) tree.

Personally, it's a model I like and I could see it working for Slackware. It would also cater for this particular scenario.

Last edited by GazL; 05-27-2018 at 08:27 AM.
 
Old 05-27-2018, 10:21 AM   #34
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,350

Rep: Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739
Have we not had that since forever?
Release - What is on the official install media.
Stable - What is on the official mirrors. The patches/ directory largely tracks changes since release.
Current - The official development tree.

What is new here is the ability to use an alternative package set based on the choice of sound server.
 
Old 05-27-2018, 10:52 AM   #35
GazL
LQ Veteran
 
Registered: May 2008
Posts: 6,873

Rep: Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982
What I was referring to was not having a patches/ directory.
 
Old 05-27-2018, 11:08 AM   #36
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,950

Rep: Reputation: Disabled
Would you mind elaborating on what are the benefits to this method and the drawback of using a patches/ directory? Seems more or less the same from my perspective, but I've never used openbsd so I could be missing some details?
 
Old 05-27-2018, 11:39 AM   #37
GazL
LQ Veteran
 
Registered: May 2008
Posts: 6,873

Rep: Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982
There's a couple of things.

Firstly, there's the fact that patches/ grows over time and obsoletes packages in the main tree, but those packages still take up space and are never removed. So that's one advantage that updating in place has. Another is that utilities like slackpkg don't need to differentiate between stable and current branches and can treat them the same (there's no patches/ to handle).

But the main point was raised in this thread. We now have two sets of alsa related packages. Where does Pat put updates? patches/ is for the main tree, where would updates for the extras go?

There's plenty of ways this could be handled of course. I was merely asking if what I outlined had ever been considered.

Don't get too hung up on the OpenBSD reference, it really doesn't matter. it's just one example. I'm sure other linux distros may do similar.

Last edited by GazL; 05-27-2018 at 11:41 AM.
 
1 members found this post helpful.
Old 05-27-2018, 11:49 AM   #38
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 2,454

Rep: Reputation: 8347Reputation: 8347Reputation: 8347Reputation: 8347Reputation: 8347Reputation: 8347Reputation: 8347Reputation: 8347Reputation: 8347Reputation: 8347Reputation: 8347
Quote:
Originally Posted by GazL View Post
But the main point was raised in this thread. We now have two sets of alsa related packages. Where does Pat put updates? patches/ is for the main tree, where would updates for the extras go?

There's plenty of ways this could be handled of course. I was merely asking if what I outlined had ever been considered.
It's what was done for years before there was a patches directory. While I'll probably update the /extra things in place, I can't think of any reason other than saving some storage space to move back to an in-place upgrade model for packages in the main tree. The primary drawback is that if I really mess up an upgrade (it happens, but hopefully not too often) then there's no package to fall back on unless you can find an out-of-date mirror. It's also easier to spot what has been upgraded when it's all in the /patches directory.
 
7 members found this post helpful.
Old 05-27-2018, 12:04 PM   #39
GazL
LQ Veteran
 
Registered: May 2008
Posts: 6,873

Rep: Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982
Fair enough. I couldn't remember there not being a patches/ directory. Strange how ones memory adjusts to things.
 
Old 05-28-2018, 04:33 AM   #40
NonNonBa
Member
 
Registered: Aug 2010
Distribution: Slackware
Posts: 192

Rep: Reputation: Disabled
Quote:
Originally Posted by volkerdi View Post
The primary drawback is that if I really mess up an upgrade (it happens, but hopefully not too often) then there's no package to fall back on unless you can find an out-of-date mirror.
I never got anything from you wrecking my system for the 14 years I've been using Slackware. Can't at worst the fallback (holed) packages always be found in the ISOs? What sounds good with the Gazl's proposal is you know once for all where you will find the update of any package, and you automatically get a release up-to-date when installing it from the FTPs (esp. the kernels, otherwise requiring a reboot).
 
Old 05-28-2018, 05:38 AM   #41
GazL
LQ Veteran
 
Registered: May 2008
Posts: 6,873

Rep: Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982
Since you mention it, in the model I was outlining, in addition to the "15.0-stable" tree that would be updated in-place you'd also have a static 15.0-release tree (fixed on release day). So the original packages would still be available somewhere. Obviously this takes up double the space on the server on release day, but you get some of that back from not having an ever increasing patches/ directory.

How big is 14.2's patches/ right now? (I'm running -current so I don't have it available to 'du')

And yes, being able to get an up to date install image from the 15.0-stable tree was not lost on me.

Pat's comment about the visibility offered by a patches/ directory is valid however, but one could argue that the changelog is sufficient visibility

If it were my distro, I'd do it this way, but it's not, and if Pat is content with the current approach then I'm not about to argue with him. It has worked so far.

Last edited by GazL; 05-28-2018 at 05:40 AM.
 
Old 05-28-2018, 05:54 AM   #42
drgibbon
Senior Member
 
Registered: Nov 2014
Distribution: Slackware64 15.0
Posts: 1,212

Rep: Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936
Quote:
Originally Posted by GazL View Post
Since you mention it, in the model I was outlining, in addition to the "15.0-stable" tree that would be updated in-place you'd also have a static 15.0-release tree (fixed on release day). So the original packages would still be available somewhere. Obviously this takes up double the space on the server on release day, but you get some of that back from not having an ever increasing patches/ directory.
The patch directory for Slackware only has the latest versions of whatever has been patched, so it would seem to save quite a bit of space compared with having redundant copies of all the stuff that hasn't been patched from 'release' in 'stable'.

Last edited by drgibbon; 05-28-2018 at 05:59 AM. Reason: delete some stuff
 
Old 05-28-2018, 06:16 AM   #43
GazL
LQ Veteran
 
Registered: May 2008
Posts: 6,873

Rep: Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982
Quote:
Originally Posted by drgibbon View Post
The patch directory for Slackware only has the latest versions of whatever has been patched, so it would seem to save quite a bit of space compared with having redundant copies of all the stuff that hasn't been patched from 'release' in 'stable'.
It kind of depends on your viewpoint.

On the central server and mirrors yes, but when you factor in all the bandwidth used by people having to download duplicate packages to apply patches after an install you start to see a different picture.

Which is most efficient from a pure cost perspective isn't going to be quite so black and white.

I suppose one could also initially hardlink the files between 15.0-release and 15.0-stable if server diskspace really was such an issue.

Last edited by GazL; 05-28-2018 at 06:24 AM.
 
Old 05-28-2018, 06:28 AM   #44
drgibbon
Senior Member
 
Registered: Nov 2014
Distribution: Slackware64 15.0
Posts: 1,212

Rep: Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936
Well bandwidth is a different issue, but yeah it would be nice to install and not have to patch, although the ISOs would have to be constantly updated to achieve that.
 
Old 05-28-2018, 06:32 AM   #45
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 15.0 + Multilib
Posts: 2,159

Rep: Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512
Quote:
Originally Posted by GazL View Post
<<snip>>

How big is 14.2's patches/ right now? (I'm running -current so I don't have it available to 'du')
Here you go GazL.

This is for my Slackware64 14.2 system, with an up-to-date local mirror thru Fri May 25 23:29:36 UTC 2018

Code:
# for d in slackware-14.2-32 slackware-14.2-64 ; do du -smD $d ; du -smD $d/patches ; done

8379    slackware-14.2
1831    slackware-14.2/patches
8293    slackware64-14.2
1784    slackware64-14.2/patches
HTH

-- kjh
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
alsa problem after the latest slackware-current update perfect_circle Slackware 8 04-26-2006 02:15 PM
slackware-current and alsa equinox Slackware 13 05-10-2005 03:06 AM
Alsa broke while upgrading to Slackware-current Almighty-Bob Linux - Software 5 03-16-2005 08:07 PM
alsa / slackware current / Intel i810 hjles Slackware 14 01-25-2005 06:11 AM

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

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