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 08-08-2019, 10:11 AM   #1
codeguy
Member
 
Registered: Jan 2004
Distribution: Slackware
Posts: 183

Rep: Reputation: 42
-current Changes_And_Hints


A few suggestions for Changes_and_Hints file:

imapd was removed

my hostname changed to include the domain name, maybe I have a weird setup though, so others wont notice.

I think because of the gcc abi change, everything you've ever compiled is gonna need recompiled. I got weird errors when trying to compile stuff with old packages:
Quote:
sed: can't read /usr/lib64/libltdl.la
 
Old 08-08-2019, 10:21 AM   #2
codeguy
Member
 
Registered: Jan 2004
Distribution: Slackware
Posts: 183

Original Poster
Rep: Reputation: 42
Oh, and maybe mention you cant use any old TERM setting, "export TERM=xterm" if safest if you upgrade via slackpkg.
 
Old 08-12-2019, 01:09 AM   #3
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,377

Rep: Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936
Pat fixed up the missing imapd reference. TERM=linux is also fine - it's what I've been using here for a long time. I've not seen any reports or issues myself on several other machines (none of which have TERM=linux -- just the defaults) with slackpkg here.
 
Old 08-12-2019, 05:38 PM   #4
dugan
LQ Guru
 
Registered: Nov 2003
Location: Canada
Distribution: Slackware
Posts: 9,029

Rep: Reputation: 3898Reputation: 3898Reputation: 3898Reputation: 3898Reputation: 3898Reputation: 3898Reputation: 3898Reputation: 3898Reputation: 3898Reputation: 3898Reputation: 3898
Quote:
Originally Posted by codeguy View Post
Oh, and maybe mention you cant use any old TERM setting, "export TERM=xterm" if safest if you upgrade via slackpkg.
What are you talking about?
 
Old 08-12-2019, 05:46 PM   #5
codeguy
Member
 
Registered: Jan 2004
Distribution: Slackware
Posts: 183

Original Poster
Rep: Reputation: 42
https://www.linuxquestions.org/quest...-a-4175658573/

when slackpkg upgrades aaa_terminfo-6, some TERM's work, some dont.

Last edited by codeguy; 08-12-2019 at 05:49 PM.
 
Old 08-13-2019, 08:20 AM   #6
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,710

Rep: Reputation: Disabled
You should also look at the changelog file, for example this entry.

Quote:
Thu Apr 19 01:04:06 UTC 2018
Hi folks, and welcome to the third ever Slackware Mass Rebuild (and the
longest ChangeLog entry in project history). There were two primary
motivations for rebuilding everything in the main tree. The first was to
switch to the new C++ ABI. The second was to get rid of all the .la files
in the LD_LIBRARY_PATH. Really, having .la files installed has been mostly
obsolete since things began to use pkg-config instead, but it's not easy
to get rid of them unless you do it all at once. If you just take them out
of one package, any other packages containing .la files that refer to the
removed ones will be broken. We've removed a few here and there before
(and then handled any packages that had referred to them with a rebuild),
but it was time to finally remove all the ones in /lib{,64} and
/usr/lib{,64}. One of the reasons that this really needed to happen is that
many projects are starting to migrate to build systems other than autotools,
and those systems do not generate .la files. So if we didn't get rid of them
now, we might end up in a situation later on where they are being removed
by upstream and then we would have to chase down the dependency breakage and
recompile (possibly many) other packages. The .la files that are outside of
the LD_LIBRARY_PATH were not removed (and shouldn't be) - those ones are
often used by the lt_dlopen() function to load plugins and removing those
ones can break things. But those ones don't cause problems... they aren't
likely to try to infect .la files produced by other packages.
IMPORTANT NOTE: If you have any third party or other packages installed on
your system that don't come with Slackware, and those packages have installed
any .la files, it is very likely that they refer to some .la files which we
have just removed, and that trying to compile against these packages will no
longer work. Luckily, the solution is simple: remove them. This command will
remove any stale .la files from the LD_LIBRARY_PATH:
rm /{,usr/}lib{,64}/*.la
Moving forward, nothing shipped in Slackware will contain any .la files in
those directories, and any SlackBuilds intended to be used with Slackware 15.0
should contain this bit of script:
# Don't ship .la files:
rm -f $PKG/{,usr/}lib${LIBDIRSUFFIX}/*.la
In addition to those goals, the opportunity was taken to clean up slack-desc
files and make many trivial fixes to build scripts. We've also made it easy
to recompile everything again should there be a good reason to do so.
You'll also find various updates scattered throughout this long list.
Enjoy, and sorry about the bandwidth. ;-)
https://mirrors.slackware.com/slackw.../ChangeLog.txt
 
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
Minor fix to CHANGES_AND_HINTS.TXT for -current lems Slackware 0 10-24-2013 07:45 PM
[SOLVED] What package is CHANGES_AND_HINTS.TXT for Slackware 13.0? stf92 Slackware 3 10-20-2013 08:03 AM
[SOLVED] The time and effort a skimming through CHANGES_AND_HINTS.TXT can save. stf92 Slackware 4 11-15-2012 12:40 AM
Needless mention of non-SMP kernels in slackware64-current/CHANGES_AND_HINTS.TXT ? FeyFre Slackware 6 09-15-2012 03:05 PM
Staying Current (with current) hjles Slackware 1 01-21-2003 07:03 PM

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

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