• Poll for users of misc/openhab

    From Alexander Leidinger@Alexander@Leidinger.net to muc.lists.freebsd.ports on Thu Sep 11 11:21:11 2025
    From Newsgroup: muc.lists.freebsd.ports

    This is an OpenPGP/MIME signed message (RFC 4880 and 3156)

    --=_4601a7b8808e1611eb7d54e5966ff825
    Content-Transfer-Encoding: 7bit
    Content-Type: text/plain; charset=US-ASCII;
    format=flowed

    Hi,

    in ports we have openhab at version 4. Version 5.0.x is available, but
    due to FreeBSD incompatibilities in graalvm stuff - which is used inside openhab - non RuleDSL (e.g. JavaScript or Python) scripting will not
    work, MQTT HA also seems to be affected. Version 5.1.x of openhab may
    come with a more recent graalvm which allows to disable os-name checks.

    Technical details:
    https://github.com/openhab/openhab-addons/issues/19276

    https://github.com/oracle/graal/commit/6d441a8bb73273e286503cfd07a7292c941e6ce0

    Poll / possible way forward for us:
    1) update misc/openhab from v4 to v5, losing JS/python support for some
    months
    2) keep misc/openhab at v4 until a fixed version is available
    3) 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)

    Opinions from FreeBSD users of openhab are welcome.

    Bye,
    Alexander.

    P.S.: the openhab developers are of the opinion, that nobody is using it
    on FreeBSD (https://github.com/openhab/openhab-addons/issues/19276#issuecomment-3250005890),
    it would be nice if users of openhab would mention their use of it on
    FreeBSD in some official openhab support channels to raise a bit of
    awareness.
    --
    http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF

    --=_4601a7b8808e1611eb7d54e5966ff825
    Content-Type: application/pgp-signature;
    name=signature.asc
    Content-Disposition: attachment;
    filename=signature.asc;
    size=833
    Content-Description: OpenPGP digital signature

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmjClJUACgkQEg2wmwP4 2IY3cA//QaeWbST6KjAHtUAqX+QiSUDSsfMIt5ULY9RNX/VmRcxLK5zFKk5UMCze D52EZEVgbQEmG0QufBdze0POvGkmqDbY8fTT8p1gJSqx4YZlgjBCAh/ej2exAq+g ThmcuJXRxKI8roaRAdR/Uh8hXF0EnjoZLsjJxWrCaxZgdisSGd/tDIaJ8KFq1Swj g016kXH0CvNTn0kv9W9rcif8SSgyc2MunjLejBHY9y0GWTqraFG3qoAnvfD1l6fG FezKCuFbpTUhekoprXkKh9SQwZT7mmlQQxXnVHrVKeQOa+oonXhL4tiYNQWBCKT0 ZImq8e4SCRh0bszqJx9ch1Ix+9ABRvKkhYgcycmVP2UdUJRkWkl3EowsTxtC8Fxp MIToeoWFmmEPBO4xdTShV1fXl2UgIYvwTmw2RQrvFgdPqi9ZqMekOWr5BljhuOCt oaP2EQYaN9WPrTm6KK7pLcf4RajMhUTLjeGqr2lExWMLMISZ/jTSYw8ibkcMis29 xurkWxTy9JRXrAln2UgBmcOiSJSgTZc8nR4r+aGsOPjhEKnrTOpDujHc4drp0Vc4 0u40hgPaGVMpwV8F4U8n0CbV/M2ifiiHV86xoaKEE4CAoC8t6d8HBjJzxRPN7SM0 sf5UHFMhlOwQa1BIyWT+arb7Ug7dS8NtsncCCX40xF/STCDvoLA=
    =64ug
    -----END PGP SIGNATURE-----

    --=_4601a7b8808e1611eb7d54e5966ff825--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Andrea Cocito@andrea@cocito.eu to muc.lists.freebsd.ports on Thu Sep 11 17:46:24 2025
    From Newsgroup: muc.lists.freebsd.ports

    On 11 Sep 2025, at 11:22, Alexander Leidinger <Alexander@leidinger.net> wrote:

    Poll / possible way forward for us:
    1) update misc/openhab from v4 to v5, losing JS/python support for some months
    2) keep misc/openhab at v4 until a fixed version is available
    3) 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, IrCOm going to go be it a try right in the weekend.
    As a rCLnon userrCY so far, take this opinion as JMH one.
    If I understand well option 1 means a loss of features potentially in use from someone, option 2 means slowing the upgrade.
    Sad to say: my advice is for #3, make a separate port, mark the old one as rCLfeature freeze, unsupportedrCY and go on.
    Keep an eye on dependencies, itrCOs unlikely but if some other port depends on the current one/versionrCa drop a note to the maintainers. Cheers,
    A.
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2