LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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 12-23-2015, 12:09 PM   #16
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,092
Blog Entries: 3

Rep: Reputation: 324Reputation: 324Reputation: 324Reputation: 324

Well then I guess people that are using slackpkg and the person packing that tarball of scripts. they should not keep sending it out like this.
Code:
#
# aaa_elflibs can't be updated.
#
aaa_elflibs
Pat a few years back said hey you can upgrade them. But the person that is maintaining slackware "Pat"keeps putting slackpkg in with the same blacklist. Now slackpkg has been upgraded a couple times now and it is still there. The confusion is at the people maintaining the distribution that keep sending the tools to the users. So I remember when Slackpkg was not Part of the distro it was an extra.
You may want to patch that blacklist and get some slack back. Praise Bob.
I know it is a conspiracy.
 
Old 12-23-2015, 01:42 PM   #17
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,148

Rep: Reputation: 583Reputation: 583Reputation: 583Reputation: 583Reputation: 583Reputation: 583
That's the point - it doesn't say that any more in the default slackpkg.conf :-)
 
Old 12-24-2015, 04:11 AM   #18
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware
Posts: 592

Rep: Reputation: Disabled
The default blacklist in -current reads as follows:

Code:
# This is a blacklist file. Any packages listed here won't be
# upgraded, removed, or installed by slackpkg.
#
# The correct syntax is:
#
# To blacklist the package xorg-server-1.6.3-x86_64-1 the line will be:
# xorg-server
#
# DON'T put any space(s) before or after the package name or regexp.
# If you do this, the blacklist will NOT work.

#
# Automated upgrade of kernel packages aren't a good idea (and you need to
# run "lilo" after upgrade). If you think the same, uncomment the lines
# below 
#
#kernel-firmware
#kernel-generic
#kernel-generic-smp
#kernel-headers
#kernel-huge
#kernel-huge-smp
#kernel-modules
#kernel-modules-smp
#kernel-source

#
# aaa_elflibs should NOT be blacklisted!
#

# You can blacklist using regular expressions.
#
# Don't use *full* regex here, because all of the following 
# will be checked for the regex: series, name, version, arch, 
# build and fullname.
#
# This one will blacklist all SBo packages:
#[0-9]+_SBo
 
Old 12-24-2015, 07:45 PM   #19
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,092
Blog Entries: 3

Rep: Reputation: 324Reputation: 324Reputation: 324Reputation: 324
Quote:
Originally Posted by rworkman View Post
That's the point - it doesn't say that any more in the default slackpkg.conf :-)
point is happy Xmas took four years read the way back machine. I know i get high.
 
1 members found this post helpful.
Old 12-24-2015, 09:01 PM   #20
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,148

Rep: Reputation: 583Reputation: 583Reputation: 583Reputation: 583Reputation: 583Reputation: 583
Satisfying Solstice to you as well
 
Old 06-15-2016, 01:28 PM   #21
hendrickxm
Member
 
Registered: Feb 2014
Posts: 201

Rep: Reputation: Disabled
Has it ever been considered to add some kind of way to inform a user that installing/upgrading package X will override files owned by other packages?
I use CRUX and when you upgrade/install a package, it sometimes contains a newer executable/library that will override an older one. An example is sulogin that used to be from sysvinit but changed to the one that comes with util-linux.

The document sums it up here:
Code:
Slackware current branch
````````````````````````

3. You should not upgrade aaa_elflibs in -current that's old and stale _after_
   other upgrades.
   For example: if aaa_elflibs was updated two months ago in -current, but you
   skipped it and upgraded other packages, you should not go back and upgrade to
   that aaa_elflibs because there is a possibility that it'll downgrade to
   previous versions of libraries.  This is because some packages such as CUPS
   do not version their library file names.
 
Old 06-15-2016, 02:04 PM   #22
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 1,173

Rep: Reputation: 3117Reputation: 3117Reputation: 3117Reputation: 3117Reputation: 3117Reputation: 3117Reputation: 3117Reputation: 3117Reputation: 3117Reputation: 3117Reputation: 3117
Quote:
Originally Posted by hendrickxm View Post
Has it ever been considered to add some kind of way to inform a user that installing/upgrading package X will override files owned by other packages?
I use CRUX and when you upgrade/install a package, it sometimes contains a newer executable/library that will override an older one. An example is sulogin that used to be from sysvinit but changed to the one that comes with util-linux.
That's a CRUX bug then. In Slackware -current there is only one sulogin, and it is found in the shadow package.

Not to say there aren't a few overlaps in Slackware, but generally these will be lesser used things and have been deemed "mostly harmless".

Quote:
The document sums it up here:
Code:
Slackware current branch
````````````````````````

3. You should not upgrade aaa_elflibs in -current that's old and stale _after_
   other upgrades.
   For example: if aaa_elflibs was updated two months ago in -current, but you
   skipped it and upgraded other packages, you should not go back and upgrade to
   that aaa_elflibs because there is a possibility that it'll downgrade to
   previous versions of libraries.  This is because some packages such as CUPS
   do not version their library file names.
You'll notice that lately every time any library in Slackware -current is upgraded, and it's a library that also has a copy in aaa_elflibs, that aaa_elflibs is also respun. So hopefully there will never be a case where aaa_elflibs in -current is stale.
 
8 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
Strategies for managing very frequent Fedora package updates? penyuan Fedora 5 08-23-2014 03:06 AM
First release of compat32pkg. A simple tool for managing package to format compat32.. phenixia2003 Slackware 12 09-24-2010 07:02 AM
Problem in package managing through GUI zombiechum Linux - Networking 1 11-04-2009 05:50 PM
package managing questions for newbie wakeboarder3780 Slackware 9 04-25-2006 07:13 PM
Slackware package managing system moses Slackware 11 01-08-2003 01:55 AM


All times are GMT -5. The time now is 12:17 PM.

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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration