Date: Sat, 07 Dec 2024 20:52:53 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 283175] graphics/materialx: MaterialX is an open standard for the exchange of rich material. Message-ID: <bug-283175-7788-QwOUhWSACm@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-283175-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-283175-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283175 --- Comment #2 from Martin Filla <freebsd@sysctl.cz> --- (In reply to Daniel Engberg from comment #1) Port maintenance: I do actively maintain my ports, but I=E2=80=99ve been ha= ving issues with Portfallout emails not reaching me. This makes it harder to address is= sues promptly. I=E2=80=99ll look into resolving this to ensure I stay on top of = any problems. Waterfox: I acknowledge that the current state of the Waterfox port on Free= BSD isn=E2=80=99t ideal. The issue is tied to Python and the latest Waterfox ve= rsion, and I=E2=80=99m working on a fix. However, it=E2=80=99s proving to be more comp= lex than expected and requires additional time or changes. Sorting Makefile entries: I=E2=80=99ve used both portlint and portclippy to= sort the Makefile entries, as recommended. However, I=E2=80=99ve received conflictin= g advice from others on which tool to use. It would be helpful if the community could agree on a standard approach. Standardization: I=E2=80=99d really appreciate clearer, unified rules and t= ools that the community agrees on. The current inconsistency makes the process more challenging and time-consuming. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-283175-7788-QwOUhWSACm>