On 2025-09-11 08:46, Andrea Cocito wrote:
On 11 Sep 2025, at 11:22, Alexander Leidinger <[email protected]> wrote:As a long-time maintainer. It seems reasonable to add v5 as a "devel" port. Thereby keeping v4 available and then useful once it's fixed. This is not a terribly uncommon case.Poll / possible way forward for us:1) update misc/openhab from v4 to v5, losing JS/python support for some months2) keep misc/openhab at v4 until a fixed version is available3) copy misc/openhab to misc/openhab4 and have misc/openhab at v5 (but then I would not do a run-test of v4 anymore... this is my least preferred way)First of all thank you. I did not know openhanded but, as a KNX hacker, I’m goingto go be it a try right in the weekend. As a “non user” so far, take this opinion as JMH one.If I understand well option 1 means a loss of features potentially in use fromsomeone, option 2 means slowing the upgrade. Sad to say: my advice is for #3, make a separate port, mark the old one as “feature freeze, unsupported” and go on.Keep an eye on dependencies, it’s unlikely but if some other port depends on thecurrent one/version… drop a note to the maintainers.
So: 1) add <category>/openhab-devel 2) keep <category>/openhabThis of course, assumes you (or somebody) would maintain the openhab-devel port :)
This also assumes that openhab gets fixed reasonably soon. I don't see any other way forward.
Cheers, A.
HTH --Chris -- Sent from hardware running on and written by FreeBSD.
0xE512722F.asc
Description: application/pgp-keys
