[SOLVED] Checkout the Current Changelog

ponce · 04-19-2018, 08:56 AM

they are cited in the ChangeLog

Quote:

Originally Posted by Pat in the ChangeLog

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.

hitest · 04-19-2018, 09:00 AM

Quote:

Originally Posted by dive

I hope you didn't have any problems with the changelog email?

I just checked my Sent folder and it's 1562 lines long. The subject alone is 190 lines!

Thanks dive! No problems with receiving your changelog e-mail. Yes. This changelog is the biggest changelog in Slackware history.

allend · 04-19-2018, 09:01 AM

Quote:

A CD/DVD subscription might be another option (if you don't have this already) but you should note that it starts from 14.2. Also I am not sure how many people still use these for install.

I collect the DVDs as souvenirs and emergency boot disks. Also useful for installing VMs, setting up PXE boots (thanks Alien_Bob!) and accessing source code.
I am happy to pay the money. If the disk arrives in the mail, that is a bonus! So far, it has _never_ failed to arrive.

PS - Maybe I am not as old as I thought. I have never seen a Mass Rebuild before. Love the attitude, clear the decks, close the hatches and dive, dive, dive!

sombragris · 04-19-2018, 09:04 AM

I love the smell of fresh ChangeLogs in the morning...

bassmadrigal · 04-19-2018, 09:07 AM

Quote:

Originally Posted by allend

PS - Maybe I am not as old as I thought. I have never seen a Mass Rebuild before. Love the attitude, clear the decks, close the hatches and dive, dive, dive!

I think he is probably referring to the a.out to ELF transition (~1995), Slackware64 (~2009), and now this.

cwizardone · 04-19-2018, 09:12 AM

Quote:

Originally Posted by slackb0t

I was thinking the same thing.. might just stay with the current -current until 15 comes out. However, I have done every other update with current since 14.2 and things have always worked. Blah.. ok I talked myself into it... I will try it

:P

A kernel update was released early this morning, so I think I'll wait until it is available in -current and then download a -current.iso and do a fresh installation.

HQuest · 04-19-2018, 10:01 AM

Quote:

Originally Posted by ponce

they are cited in the ChangeLog

Yep, shame on me. Too many things on a single ChangeLog.

Upgraded two of my dev servers, rebuilt/updated two of my custom packages, everything works like a champ.

orbea · 04-19-2018, 10:14 AM

Quote:

Originally Posted by Didier Spaier

Right:

Code:

didier[~]$ PKG=somepackage
didier[~]$ set -B
didier[~]$ echo $PKG/{,usr/}
somepackage/ somepackage/usr/
didier[~]$ set +B
didier[~]$ echo $PKG/{,usr/}
somepackage/{,usr/}
didier[~]$

However, "set -o posix" doesn't change the default behavior.

There are more bashisms in the Slackware scripts and there have been threads about that in the past:
https://www.linuxquestions.org/quest...-s-4175507325/
https://www.linuxquestions.org/quest...on-4175502351/
https://www.linuxquestions.org/quest...ten-in-849052/
https://www.linuxquestions.org/quest...13-0-a-778084/

You should test with dash instead of "set -o posix". Bash is not reliable at testing portability. The best way to do that is to actually test other shells, the checkbashisms script and shellcheck can help to some degree.

Code:

$ dash
$ echo {foo,bar}
{foo,bar}

Brace expansions only work in bash, zsh, ksh and shells derived from ksh (excluding posh).

Quote:

Originally Posted by Didier Spaier

Those who want their scripts to behave as sh will rewrite the command, no big deal.

Editing every SlackBuild on every update would be a giant pain, but more than that I don't want to find my own scripts at SBo are full of brace expansions when 15.0 is released.

Edit: Also, as a side note, "set -o posix" is of course not posix...

http://pubs.opengroup.org/onlinepubs...hap02.html#set

Darth Vader · 04-19-2018, 10:51 AM

Then, is the time for the resident shell scripting Gurus to propose a better solution...

I guess our BDFL will be glad to consider their proposals.

orbea · 04-19-2018, 11:09 AM

Quote:

Originally Posted by Darth Vader

Then, is the time for the resident shell scripting Gurus to propose a better solution...

I guess our BDFL will be glad to consider their proposals.

I am no guru, but its not hard. This should be portable.

Code:

find $PKG/lib${LIBDIRSUFFIX} $PKG/usr/lib${LIBDIRSUFFIX} -type f -maxdepth 1 -iname '*.la' -exec rm -f {} \;

Or

Code:

rm -f $PKG/lib${LIBDIRSUFFIX}/*.la $PKG/usr/lib${LIBDIRSUFFIX}/*.la

khronosschoty · 04-19-2018, 11:15 AM

Quote:

Originally Posted by orbea

I am no guru, but its not hard. This should be portable.

Code:

find $PKG/lib${LIBDIRSUFFIX} $PKG/usr/lib${LIBDIRSUFFIX} -type f -maxdepth 1 -iname '*.la' -exec rm -f {} \;

Or

Code:

rm -f $PKG/lib${LIBDIRSUFFIX}/*.la $PKG/usr/lib${LIBDIRSUFFIX}/*.la

The nice thing about Pat's solution (the one with the bashism) is it will remove the .la files on a multilib system; in just one little line.

orbea · 04-19-2018, 11:29 AM

I'm talking about the command that would be added to build scripts to prevent .la files from being reinstalled and not the command you ran in your interactive shell to remove no longer needed .la files.

khronosschoty · 04-19-2018, 11:37 AM

Good point.

Didier Spaier · 04-19-2018, 11:59 AM

Quote:

Originally Posted by orbea

Edit: Also, as a side note, "set -o posix" is of course not posix...

Right, you made my day

The best way to check portability is to look into the POSIX specification. Of course it is not mentioned there and this answers that.

This reminds me the old saying "This algorithm has been proven to provide the right result but be careful, I didn't test it yet".

Darth Vader · 04-19-2018, 12:08 PM

I believe that this noble issue of shell scripting is worth for its own thread.

Now let's focus in the main dish. Since years, many of us advocated/lamented for "a clean and rebuildable Slackware tree", and today those dreams became true*: our BDFL and his lieutenants served us the entire hog at roast.

So, first of all, I think we should figure out how to eat and digest it, preferable avoiding the "hospitalization" ...

-------------------
* With a bit of "be careful what you wish"...