New packages: fl{aa,amp,cluster,log,msg,net,wkey,wrap}

[Goorzhel]

/label new-package wip
@classabbyamp (#38771 (comment))

I need help with:

1. picking a good name for the meta-package (fldigi-full was a wild guess),
2. fl{amp,cluster,msg} failing to set USE_X (I left a writeup in the flamp template), and
3. the applications that do build presenting an all-black theme: black font on black background. Just my machine (running sway), or something wrong with the way I built the programs?

Testing the changes

• I tested the changes in this PR: briefly

New package

• This new package conforms to the package requirements: YES

[classabbyamp]

I'm not sure we need a metapackage for all of them

[Goorzhel]

fl{amp,cluster,msg} failing to set USE_X

I was missing hostmakedepends="pkg-config".

[classabbyamp]

can confirm the weirdness. Also, I don't appear to be able to open any of the menus at the top, fllog just freezes

[classabbyamp]

ok the same colour thing is happening in fldigi, but not flrig

[Goorzhel]

I could reproduce the weirdness of flamp on two OSes set up somewhat identically (i.e., running sway upon seatd):

• FreeBSD 13.1-R, pkg install -y flamp
• NixOS 22.05.2512.a82127cea64, built from upstream tarball in nix-shell -p pkgconfig -p fltk

@classabbyamp doesn't use Wayland, so it's probably not something specific to Wayland either. (Even so, I should try to reproduce this in an X environment.) Nor does it seem specific to fltk alone, because dillo is built on fltk and I saw no problems there.

[classabbyamp]

I think this is something to bring up upstream

[Goorzhel]

ok the same colour thing is happening in fldigi, but not flrig

On FreeBSD, both work. On NixOS, flrig works, and fldigi behaves like flamp.

I think this is something to bring up upstream

Agreed. I'll submit a bug report eventually.

[Goorzhel]

I left fltk-devel as a depends in one of the packages. 🤡

EDIT: I also sent that bug report.

[Goorzhel]

The problem went away for @classabbyamp (bspwm), but not for me (sway). I definitely need to try an X environment.

[Goorzhel]

I tried six different environments — {{Void,FreeBSD} laptop,NixOS VM} plus {sway,i3} — and the fltk test programs displayed correctly only on the NixOS VM, in both X and Wayland.

I wanted to figure out what NixOS was doing differently, but I went about it in a very caveman-like way: I went back to the Void system and tried compiling with each dependency I figured I was missing, one-by-one:

$ xi -y libXft-devel
$ ./configure && make -j8 && test/preferences && make clean
$ # and so on, for libX{inerama,cursor,fixes,...}

But I couldn't get the all-black UI to go away. I also tried ./configure --enable-local{jpeg,zlib,png} — same behavior.

There is almost certainly something very stupid I'm missing. But I'll devote some more time to finding it before asking up-upstream.

[github-actions]

Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.

[Goorzhel]

I was close to giving up on this but there's less work left than I thought. I just need to redo the fltk tests, take some screenshots, and file an issue at github.com/fltk/fltk.

[Goorzhel]

Well, damn. I downloaded the latest FLTK snapshot (fltk/fltk@e7eac09c), compiled the tests, and saw them display perfectly. Then I downloaded the 1.3.8 release separately, compiled the tests there*, and got that all-black UI again.

It seems this is stuck until FLTK 1.4.

* ./configure && make -j8 && ./test/preferences

[Goorzhel]

@classabbyamp, if you have a spare moment can you download the two tarballs I linked above and try ./configure && make -j8 && ./test/preferences inside each of them?

[github-actions]

Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.