I would like to suggest to use the latest code from the git repository for libimobiledevice. As the 1.2.0 version does not work with iOS 11.

I checked out the vlan branch of*git://git.rlworkman.net/slacknetsetup on a new slackware64-current installation on my laptop (wlan0 with an IP and wlan0.4 with an IP address). This seems to work, as long as the configuration of wlan0 comes before wlan0.4.

Now I want to volunteer to start IPv6 support.
I already tested what would happen if I put a static IPv6 address instead of an IPv4 address in rc.inet1.conf, and the address actually gets assigned to the network interface. I don't think this is really an option for the long term because it doesn't solve anything for people who want to have both IPv4 and IPv6 addresses on a network card. There is also some IPv4-specific logic in the handling of IPADDR[0] etc.

I would suggest 2 new config variables:
IP6ADDRS[0] and IP6CONFIGTYPE[0].
IP6ADDRS[0] can contain one or more IPv6 addresses for static IP address assignment.
IP6CONFIGTYPE[0] (comparable to USE_DHCP[0] for IPv4) can contain either "Static" or "Autoconfig". I have no experience with DHCPv6, so maybe that needs to be a third option for IP6CONFIGTYPE[0].

What do you think?

I e-mailed my SSH public key to Robby Workman, so if he approves, I will start working on this.

If anyone else has ideas or wants to give me their DHCPv6 setup, that is also greatly appreciated.

I'm also entertaining the idea of building tunnels into rc.inet1 (like for https://www.tunnelbroker.net/), do you think that would be useful?

Hi,

geeqie-1.4 is released.
http://geeqie.org/geeqie-1.4.tar.xz

e2fsprogs-1.43.8:

https://git.kernel.org/pub/scm/fs/ex...96980e16c8ab19
https://www.kernel.org/pub/linux/ker...-1.43.8.tar.xz

LibreOffice ?

I replied to your mail with lots of stuff :-)

On one hand, I think it's a useful addition - it's IMHO the best office suite available.

On the other hand, having it outside the main tree makes it easier to keep it updated - quite frankly, I can almost promise that you won't see routine upgrades, even within a minor -stable series, if it goes into the main Slackware tree.

Hi,

That's mine opinion too.
The same goes for SMplayer (which I maintain at SBo) and Geany, which were requested here.

--
Best regards,
Andrzej Telszewski

dhcpcd-7.0.0:

https://roy.marples.name/archives/dh...s/0001903.html
https://roy.marples.name/git/dhcpcd.git/
ftp://roy.marples.name/pub/dhcpcd/dhcpcd-7.0.0.tar.xz

gdbm-1.14:

http://git.gnu.org.ua/cgit/gdbm.git/log/
ftp://ftp.gnu.org/gnu/gdbm/gdbm-1.14.tar.gz

I hope that the Slackware Team is well aware that those words apply well also to a particular Desktop Environment with a life cycle of roughly a month and so big that represents roughly half of our typical Slackware distribution.

Yeah, I talk about the glorious ugly Plasma 5.

As much I love the KDE, I cannot be not aware that the today KDE and the future Plasma is just like a Cancer which parasite our beloved Slackware.

Permit me to believe that this is proper way to threat also the "KDE5", aka Plasma 5: a separate repository, even it is an official one, able to follow its one month release cycle and to not pollute the main tree.

No, I do not want Patrick Volkerding to transform in a "Plasma packager", but to stay as he done in the last 25 years: a Linux packager and maintainer.

Heck! We arrived to be the biggest distribution which ship monolithic, partially blaming our lack of dependencies resolution, but mainly thanks of that huge tumor on the face of Slackware: KDE.

Let's be honest to ourselves: there are so many things beyond KDE. That Cancer should be extirpated with no mercy.

The quote loses the original text - but in this case, the suggestion was "LibreOffice"
Robby - I absolutely see your point. But, it could be just as easy to say that for virtually every single other package on the iso too. Firefox, Thunderbird, etc. Point is that if one wants to take the full iso and put it on Granny's PC, Granny will really want to a) browse the web, b) send some email, and c) type up some old-fashioned letters. The standard Slackware install satisfies a) and b), but the packages that ship to satisfy c) are really a bit "weak" or "wanting". Really, LO is the only game in town.
I know some people might say that Slackware isn't suited to Granny - but I'm sick and tired of installing Ubuntu and then having to deal with its chronic update cycle which seems to break things more often than I'd care. Slackware is, to my mind, the perfect distro for Granny - install it and forget it - Granny will be happy for years to come.

A TWO year old SMPlayer is still well functional, because they does not change too much the main features. And probably it will be in pair with the shipped MPlayer. Trust there a lifelong SMPlayer user: me.

BUT, of course, why we should make the Slackware users life easy? ;)

According with the honorable Scholars hanging here, the typical Granny buy a 8GHz 32 cores Ryzen, assorted with 64 GB DDR4 memory and at least a Tesla unit, and she love to build the Qt5 and LibreOffice from sources. ;)

Hi,

But in the 2 years, they have fixed multiple bugs.
The bugs might not apply to your use case, but might to others.

And I generally keep SMplayer reasonably updated at SBo.
You can't expect the same from Pat in general, because he might not be using the software in question, and until somebody comes to LQ and asks for an update, Pat might not notice the need.

I just don't see a need for that.
Of course, your opinion might be different.

--
Best regards,
Andrzej Telszewski

Again, a TWO years old SMPlayer, probably in pair with the very MPlayer shipped, is much better than nothing. ;)

And I was never bitten by a SMPlayer bug, while watching the usual files.

Also, not every Granny is a hacker, you know... :p

PS. WHY YOUR SMPLAYER ask me for updating, no longer than today?

Hi,

Mine is only SlackBuild :->

If
does not speak to you, then please try:
"Preferences -> Updates -> Check for updates (untick)" and you'll be all set.

--
Best regards,
Andrzej Telszewski

Should Slackware not include a kernel since they put out a new one every month or two (-current's gone through 36 kernels so far)? Mesa has been upgraded 28 times during this development cycle... should we leave that out too so users can update it when new releases are out? Firefox was upgraded 23 times and Thunderbird was upgraded 18 times. Should these be left out as well to ensure that users can keep on top of them? For comparison's sake, there's been 17 months since 14.2 was released, so all of these have an average of at least an upgrade a month.

This is no different than ANY other piece of software on Slackware. Some have predictable release schedules, while others follow a "release it when it's ready". Pat will do as he always does and find the balance between recent and stable. I have no doubt this will occur with KDE5 if it is included. He will find a release that works well, and if there are serious bugs, he'll put out patches... just like he has done for previous KDEs.

And KDE 5.12 is supposed to be an LTS release with "at least 2 years of support" (which works out since it coincides with an LTS release of QT 5.9).

For any curious, the command I used to find the number of times a program changed is:

Dear Frenemy, in your wonderful speech you have fantasies like a hypothetically KDE 5.12 ...

The harsh reality is that we have expect in the near future the Plasma 5.12 (and this will be LTS), the Frameworks 5.42 or something (and this will NOT be LTS) and probably the Applications 18.1.0 (also this will NOT be LTS)

There is no such thing like KDE 5.12, just like Santa Claus does not exists.

Instead, we have tons of stand-alone applications and frameworks, with a life cycle of one freaking month.

Should Patrick Volkerding track down those hundreds of projects, and spend his half of time going to figure out how they work together, in defavor of other distribution components?

In my opinion, this should not happen.

Instead, the Plasma should go in its own repository, even it will be maintained also by our BDFL, out of enthusiasm.

WHY? Because a separate repository for Plasma 5 will permit a separate release cycle, maybe similar with a forever -current. ;)

BUT, every bit of KDE, Plasma or whatever better to go away from the main tree. Heck, the Plasma 5 is big enough to be shipped in its own DVD!

I do this discourse because I believe that Slackware is a general purpose operating system and definitively NOT a desktop one.

And this very idea imply that I should have the ability to install Slackware without any bit of a particular DE.

Hi,

You're going to receive a well known answer (TM) to this claim, if any.

--
Best regards,
Andrzej Telszewski

Do you realize that Pat has handled previous KDEs without an issue? He will likely find a version that is stable in Slackware and then just push out patches as needed. Just because KDE devs have their own release schedule doesn't mean that Pat has to put out every single release they have.

And I know "KDE5" doesn't exist, but it is much easier for me to call it that.

I know about the Holly Full Install, and I will happy to follow it, when I need that.

The issue is that that Holly Full Install should not contains any bit of KDE or Plasma.

It better should go in its own repository, from where the fans of it (including me) can install it all the way. ;)

Or we could include a fully functional KDE (with subsequent patches as Pat sees fit) and then others, who want the latest and greatest, can set up slackpkg+ (or their preferred method) to track Eric's ktown.

...which is basically the way the last few releases went (possibly longer, but I wasn't paying enough attention back then). :hattip:

Let me respond to you with your own words:

"-1000000 for that. To intentionally broke even those small bits of compatibility with (..)"

About what KDE you talk with serenity, when the last one of its kind is KDE4, and sooner or later it will not compile anymore?

In other hand, I do not see our BDFL pushing in patches half of distribution packages, BTW... ;)

A separate official repository for Plasma 5, which gives a rolling release (monthly?) experience, independently of the main releases, probably will make even more happy the Windows fans. ;)

Darth_Vader: by your logic, Pat should stop including vim, since it averages two releases a day.

Also: one release a month isn't exactly an overwhelmingly rapid release schedule.

Can we not spam this thread with arguments about Plasma 5? This has already been discussed ad nauseam in other threads, and you can always resurrect one of them if you want to continue.

Surely not, if we talk about VIM, but when we talk about an entire ecosystem of independent applications and frameworks, compared with the Slackware's biannual release cycle, this is really overwhelming.

Also, to note that I do not talk about "stopping including" the KDE or Plasma, but giving it a more proper environment to evolve?

You will not trust a very Patrick's KTown or a separate Plasma 5 DVD? Myself I will do.

This is a proposal for -current, BTW... ;)

nano-2.9.2:

https://www.nano-editor.org/news.ph
https://www.nano-editor.org/dist/v2.9/nano-2.9.2.tar.xz

I think I understand where points @Darth Vader.

Having a separate official ktown will permit to Patrick Volkerding to leave its handling to one of his lieutenants. I cannot see one other than Eric Hameleers, though.

Also having a separate tree, will permit to give to KDE5 more releases, i.e. two times per year.

Mainly will profit from this exactly the KDE5 users.

Oh, give it a break. You know what I mean when I type KDE5.

And Pat only needs to push patches for serious issues. How many patches has he pushed to the 4.4 kernel compared to how many were put out by the kernel devs? There's been over 100 patches from the kernel devs for the 4.4 series and 14.2 has had 6 kernel patches. Stable Slackware releases don't need their software to be kept up-to-date... they just have serious bugs/vulnerabilities patched when they are found.

That's exactly what you're talking about. It would no longer be in the main distro. And then you're saying Pat should keep the first repo of official software outside of the install media? That would mean he'd likely need to add a way to add it and keep it up-to-date with the distro (maybe incorporating slackpkg+ as an official program?).

Or, he could just include it in the official release like he has with previous KDE versions and only provide patches when necessary, and then others who want to track the monthly releases could use ktown.

Stable Slackware releases are supposed to be stable (hence the name). "Evolving" software doesn't belong... but Eric provides ktown to those that are willing to use evolving KDE software releases.

But I'm not going to derail this thread further. If you want to continue to discuss this with me, open a new thread or PM me.

I think @Darth Vader mentioned a separate DVD for shipping the KDE5.

If there are so many KDE5 fans, releasing several times per year those official KDE5 compilations on DVD would likely to increase the company revenue.

Or maybe there are just few vocal fans of KDE5 and the huge majority use lighter alternatives?

According with https://www.linuxquestions.org/quest...-a-4175614638/ only 69 users voted for KDE5.

That is a sentence without value.
An absolute number has no meaning. If you check that post, the question was "do you prefer KDE4 or KDE5" and with just these two options, 72.63% chose KDE5.

Thank you, I will correct:

From the supposed Slackware community, only 95 users looks like was interested by KDE at whole, either v4 or v5.

I say "only" because a personal wild guessing is that the number of those using Slackware is much larger than that.

Want to take a guess at how representative the turnout of a poll on an internet forum is of the worldwide Slackware community?

I'll take the opportunity to repeat my recent suggestion about promoting, at some point in time, some well-known stuff from SBo/repository/*/academic, like R, Octave or Maxima (maybe OpenBLAS too) into official Slackware packages.

But my main reason to write this post is actually to say big thanks to Slackware team for all their sane choices related to packaging. Namely, recently I was involved in an intensive round of testing of some codes that I'm working on for different distributions, mostly CentOS/Fedora, then for openSUSE, and also a bit for Debian/Ubuntu. I typically don't do that part of the work, but at the end I was delighted with opportunity to learn about progress in container solutions, in our particular case about Singularity, that made it possible to actually do all of the work on a Slackware system, using lightweight containers for mentioned distributions, all supplemented by flawless handling of some complicated stuff like using host GPU(s) for computations from the container, or integration with host MPI installation. All together, indeed a perfect setup for a developer to build and test code for different distributions. On the other side, I was reminded how package handling in each of mentioned distributions is an absolute nightmare. Namely, when one works with containers the goal is typically minimal install, but with all of these insane dependency resolution chains, you just end up with installing half of the packages one way or another. Adding insult to injury is this sick practice of splitting each piece of software into multiple packages, like foo-base, foo-devel, foo-libs, foo-noarch, foo-with-bar, foo-with-baz, etc. etc. So again - thanks Slackware team for keeping it simple and manageable.

I do use a lighter alternative, but KDE Frameworks 5 is an important part of that alternative.

You'll never guess which DE Mr. Volkerding uses.

Is LuckyCyborg a pseudonym for Darth?

Xfce?

No, it's his brother :D;)

No, I am not his brother.

Darth helped Darth? Freudian slip apparently, or "alias Darth Vader=LuckyCyborg"

LOL, glad I quoted fully since it was apparently deleted....

I wanted to post a quote from a private discussion.

Still looking how to quote from a PM.

You do not need to quote from private conversations.

I take this position publicly.

geeqie-1.4
http://geeqie.org/geeqie-1.4.tar.xz

It seems to be grateful to a person who helped you is a foreign concept for some.

However, let me to quote Zhuang Zhou, the author of Chuang Tzu:
He was an adept of thinking out of box. You watch too much Mr. Robot and see conspirators everywhere.

啊，但你知道這是一個池塘，而不是井，我指導你回到蝴蝶的夢想。 讓我們不要劫持線程。

rough translation others: "Ah, but you see it is a pond and not the well, I direct you back to the butterfly dream. Let us not hijack the thread."

What kind of traffic are you getting on your Plasma builds? Willing to bet it's pretty heavy.