Re: x11/tk/8.6: Missing headers in package?

True, because it is "private" there's no guarantee. Just might be lucky, as you said.
There's a newer version at tcl3d.org that'll work with Tcl 8.6.

Stu





On Friday, September 20, 2024 at 10:23:20 a.m. EDT, Stuart Henderson <stu@spacehopper.org> wrote:





On 2024/09/20 14:10, Stuart Cassoff wrote:
> With Tcl, it's always been possible to do that; Tcl is not Python or whatever.
> This sort of backwards compatibility exists with/is a feature of Tcl.

except togl is seemingly touching Tk internals rather than public
interfaces so that is perhaps not reliable.

> Extensions built against 8.5 should be able to be loaded into 8.6 without problem.
> Certainly worth trying, imo.

togl uses TkWindow structs which are one of the things which changed
between 8.5 and 8.6 in tkInt.h. Though I guess it might get lucky as the
added members in this struct were at the end (and it doesn't seem to use
one of the structs where there were bigger changes like TkDisplay) ...


> Stu
>
>
> On Friday, September 20, 2024 at 09:29:54 a.m. EDT, Stuart Henderson <stu@spacehopper.org>
> wrote:
>
>
> On 2024/09/20 12:43, Stuart Cassoff wrote:
>
> > Private files aren't meant to be installed. They're in the 8.5 package mostly for historical
> > reasons or older ports.
> > Instead of using MODULES you could try setting BUILD_DEPENDS for 8.5 and WANTLIB and
> > RUN_DEPENDS for 8.6.
> > Something like that, maybe other vars as well.
>
>
> That (building against private headers for an old Tk version which isn't
> the version running the extension) seems like a worse idea than building
> against current version private headers (whether they come from a :patch
> target or from the package).
>
>

[revision] www/mozilla-firefox: Inform about H264 decoding in pkg-readme

Some web conferencing applications, like Webex or Jitsi-meet, require
H264 hardware decoding to work, but in Firefox, this feature is disabled
by default. To save others from going through the trouble of figuring
this out (particularly when the OpenH264 Video Codec plugin (under
about:addons -> Plugins), that supposedly "will be installed shortly",
can be quite misleading), I suggest adding the following to the
pkg-readme. sdk@ was very kind to help me figure this out.

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1717679

diff /usr/ports
path + /usr/ports
commit - c69c8333fd531f9987d5e116c0af876764be3704
blob - f5d1f06e728bb5a26889bbe6717bae0a9f6dbdac
file + www/firefox-esr/pkg/README
--- www/firefox-esr/pkg/README
+++ www/firefox-esr/pkg/README
@@ -122,6 +122,12 @@ device e.g.:
Screen sharing needs shmget() which isn't available when pledge() is active, so
you will have to disable pledge for the main process.

+Some web conferencing applications also require H264 hardware decoding, which
+by default is disabled in Firefox. To enable it, open about:config and set the
+following key to true:
+
+media.webrtc.hw.h264.enabled: true
+
KerberosV support
=================
To use Kerberized Firefox, first manually install the "heimdal" package
commit - c69c8333fd531f9987d5e116c0af876764be3704
blob - f5d1f06e728bb5a26889bbe6717bae0a9f6dbdac
file + www/mozilla-firefox/pkg/README
--- www/mozilla-firefox/pkg/README
+++ www/mozilla-firefox/pkg/README
@@ -122,6 +122,12 @@ device e.g.:
Screen sharing needs shmget() which isn't available when pledge() is active, so
you will have to disable pledge for the main process.

+Some web conferencing applications also require H264 hardware decoding, which
+by default is disabled in Firefox. To enable it, open about:config and set the
+following key to true:
+
+media.webrtc.hw.h264.enabled: true
+
KerberosV support
=================
To use Kerberized Firefox, first manually install the "heimdal" package