nwg-look 0.2.0 (2023-03-07)

[nwg-piotr]

• added fix for nwg-look -a to respect color-scheme settings by @MarkusVolk;
• added translation engine;
• added pl_PL lang.

[edit] I had to push a quick update to 0.2.1, due to the toolbar-icon-size label missing from pl_PL and written in Polish in en_US. :)

Packaging

Please note that from now on you need to copy langs to /usr/share/nwg-look/.

[mac-a-r0ni]

Just leaving comment here since it's not really a bug per-se, but on Slackware stable 15.0, this will not build. Golang can't move past 1.19 because of the gcc slackware shipped and the vendor mods call for 1.20 minimum (which I'm seeing Arch is shipping now). This is likely not an issue on the -current slackware dev systems, but I haven't had the time to test yet. We're about to enter a release beta soon enough and very likely in the next 3~ months there will be a new stable release which WILL support Go 1.20+.

This hasn't affected any other Go packages yet, but when it does, they will essentially be frozen at those versions on 15.0. I'll be returning my focus to our "rolling" dev release very soon.

[nwg-piotr]

If you can modify go.mod on your side, and if I remember well, go>1.16 should be enough.

[mac-a-r0ni]

go>1.16 should be enough.

I'll do some testing and see if I can't get a package out of it after-all!

[nwg-piotr]

Thank you. At the moment I'm a little confused by the recent contributions to nwg-panel, that introduced more bugs than features. Need to try and wrap my head around it.

[mac-a-r0ni]

I'm sure you'll get to the bottom of it! btw I fixed it, nwg-look now builds again!

[nwg-piotr]

Great! I keep on trying to keep up with golang versions, but this language evolves almost as fast as damned Android SDK. 🤣

[nwg-piotr]

SlackBuilds packages are now visible in repology badges, yay!

[nwg-piotr]

Haha, we live on the bleeding edge here on Arch. ;) Seriously: the size of the project is starting to overwhelm me. If I don't release a new version right after making changes, I may forget about them for the next six months.

[mac-a-r0ni]

Haha oh I get it. Managing projects with a considerable size things tend to get lost in the shuffle. I usually live in the unstable land of Slackware development versions so I get things immediately as well just like Arch but for those who stay on stable there is a wait time involved in their "stability". I'm generally better at keeping my own repos up to date but I've not been doing so focusing on the SlackBuilds versions, but I'm working on fixing that right now ;)

I'm working out a script to take me from stable to devel distros without any formatting etc, the biggest hurdle has become e2fsprogs which has an incompatibility with grub since an update recently. Grub needs patching on both ends before things work normally. That's all done now, so now I need to test hotswapping my OS/chroots to see if it all worked out!

[nwg-piotr]

Honestly, Slackware is a bit too geeky to my taste. In my 50s', I prefer to focus on my own ideas, instead of maintaining the system itself. Arch is rock stable, by the way.

[mac-a-r0ni]

Well any distro can be stable, if the user knows how to manage it ;)
That said, I don't have any problems overall with it besides not needing or having a use for systemd, and I really don't care for the package manager. The distro itself is fine, but if I had to use one with a overbearing package manager, I'd use Debian. I rather enjoy the freedom I have in Slackware not forcing any dependencies on me, and can make things work for me instead of conforming to someone else's standard on how something should ship. If it weren't for the abysmal hardware support, I'd be on BSD by now. But Slackware does just fine for my old tastes.

[nwg-piotr]

I must give BSD a try one day.

overbearing package manager

I'm quite happy with pacman, except for my own stuff. I use packaged versions on the testing lappy only.