• Flavors and OPTIONS

    From Koen Martens@gmc@metro.cx to muc.lists.freebsd.ports on Sat Nov 14 21:58:59 2026
    From Newsgroup: muc.lists.freebsd.ports

    Hi all!
    I'm intending to adopt the net/lambdamoo port, which is currently
    without a maintainer.-aThe current version is 1.8.1, which is ~25 years
    old.
    There's an upcoming new version which will introduce a number of new
    features (such as 64 bit integers, unicode support and more) that will
    be somewhat incompatible with databases running under version 1.8.1.
    Many of those are optional.
    To not cause too much disruption, I'd like to create two flavors: a
    default 'legacy compatible' flavor that is configured to behave like
    the 1.8.1 release and a 'modern' flavor that enables a number of the
    new features. This would create two binary packages, the default one
    being the automatic upgrade path when using binary packages, and the
    new available for admins that want to migrate their moo database to
    make use of the new features.
    However, I would also still provide the ability to manually configure
    the port and enable individual features.
    I think I can get what I want by defining options for all the features
    and then define OPTIONS_FILE differently for the two flavors as well as providing different OPTIONS_DEFAULT values for the flavors.
    I see other ports doing similar things, so it's not without precedent,
    but I'm curious whether that's the canonical way to go about it or
    whether there are other ways of going about this.
    Cheers,
    Koen
    --
    Software architecture & engineering: https://www.sonologic.se/
    Sci-fi: https://www.koenmartens.nl/
    Retro computing:-ahttps://video.chasmcity.net/c/scandinavianretro/videos
    --
    Software architecture & engineering: https://www.sonologic.se/
    Sci-fi: https://www.koenmartens.nl/
    Retro computing:-ahttps://video.chasmcity.net/c/scandinavianretro/videos
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Abdelkader Boudih@seuros@FreeBSD.org to muc.lists.freebsd.ports on Sat Nov 14 21:17:00 2026
    From Newsgroup: muc.lists.freebsd.ports

    --15a472c8425882b00a669516c8f698991c632186
    Content-Type: text/plain
    Content-Transfer-Encoding: 7bit

    I think you can just bump to a major version and have an upgrade flow if possible.

    People using it are tech savvy. And a Major version always signal possible breaking changes.

    Regards,
    Abdelkader

    --15a472c8425882b00a669516c8f698991c632186
    Content-Type: text/html
    Content-Transfer-Encoding: 7bit

    <!DOCTYPE html><html><head><title></title></head><body><div>I think you can just bump to a major version and have an upgrade flow if possible.<br></div><div><br></div><div>People using it are tech savvy. And a Major version always signal possible breaking changes.</div><div><br></div><div>Regards,</div><div>Abdelkader</div><div><br></div></body></html>
    --15a472c8425882b00a669516c8f698991c632186--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Koen Martens@gmc@metro.cx to muc.lists.freebsd.ports on Sun Nov 15 08:29:55 2026
    From Newsgroup: muc.lists.freebsd.ports

    --=-rbvYKpcrHIE6KxeP2lH4
    Content-Type: text/plain; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable

    On Sat, 2026-11-14 at 21:17 +0000, Abdelkader Boudih wrote:
    I think you can just bump to a major version and have an upgrade flow
    if possible.

    The version number is not under my control, and the intention of
    upstream is explicitly to have both the 'legacy' configuration and the
    more modern configuration to co-exist.

    Migrating an existing database is not trivial. For my own moo, I intend
    to run 1.9.0 with the 'legacy' configuration for the time being while I investigate what I need to do to upgrade the database. The one and only LambdaMOO itself expects to migrate to the modern features over a
    period of several years.

    People using it are tech savvy. And a Major version always signal
    possible breaking changes.

    Yes, but people running it may not have the time to invest to carry out
    a migration on their database that will take them days to figure out
    what in their specific database requires attention with the new
    features right when the new release is forced upon them, so a
    transition period where both are available is definitely needed.

    Cheers,

    Koen

    --=20
    Software architecture & engineering: https://www.sonologic.se/
    Sci-fi: https://www.koenmartens.nl/
    Retro computing:=C2=A0https://video.chasmcity.net/c/scandinavianretro/video=
    s

    --=-rbvYKpcrHIE6KxeP2lH4
    Content-Type: text/html; charset="utf-8"
    Content-Transfer-Encoding: quoted-printable

    <html><head><title></title><style>pre,code,address {
    margin: 0px;
    }
    h1,h2,h3,h4,h5,h6 {
    margin-top: 0.2em;
    margin-bottom: 0.2em;
    }
    ol,ul {
    margin-top: 0em;
    margin-bottom: 0em;
    }
    blockquote {
    margin-top: 0em;
    margin-bottom: 0em;
    }
    </style></head><body><div>On Sat, 2026-11-14 at 21:17 +0000, Abdelkader Bou= dih wrote:</div><blockquote type=3D"cite" style=3D"margin:0 0 0 .8ex; borde= r-left:2px #729fcf solid;padding-left:1ex"><div>I think you can just bump t=
    o a major version and have an upgrade flow if possible.</div></blockquote><= div><br></div><div>The version number is not under my control, and the inte= ntion of upstream is explicitly to have both the 'legacy' configuration and=
    the more modern configuration to co-exist.</div><div><br></div><div>Migrat= ing an existing database is not trivial. For my own moo, I intend to run 1.= 9.0 with the 'legacy' configuration for the time being while I investigate = what I need to do to upgrade the database. The one and only LambdaMOO itsel=
    f expects to migrate to the modern features over a period of several years.= </div><div><br></div><blockquote type=3D"cite" style=3D"margin:0 0 0 .8ex; = border-left:2px #729fcf solid;padding-left:1ex"><div>People using it are te=
    ch savvy. And a Major version always signal possible breaking changes.</div= ></blockquote><div><br></div><div>Yes, but people running it may not have t=
    he time to invest to carry out a migration on their database that will take=
    them days to figure out what in their specific database requires attention=
    with the new features right when the new release is forced upon them, so a=
    transition period where both are available is definitely needed.</div><div= ><br></div><div>Cheers,</div><div><br></div><div>Koen</div><div><br></div><= div><span><pre>-- <br></pre><div>Software architecture &amp; engineering: <=
    a href=3D"https://www.sonologic.se/">https://www.sonologic.se/</a></div><di= v>Sci-fi: <a href=3D"https://www.koenmartens.nl/">https://www.koenmartens.n= l/</a></div><div>Retro computing:&nbsp;<a href=3D"https://video.chasmcity.n= et/c/scandinavianretro/videos">https://video.chasmcity.net/c/scandinavianre= tro/videos</a></div></span></div></body></html>

    --=-rbvYKpcrHIE6KxeP2lH4--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From ronald@ronald@FreeBSD.org to muc.lists.freebsd.ports on Sun Nov 15 10:07:31 2026
    From Newsgroup: muc.lists.freebsd.ports


    Op zaterdag 14 november 2026 21:58:59 (+01:00) schreef Koen Martens:
    Hi all!

    I'm intending to adopt the net/lambdamoo port, which is currently
    without a maintainer.-aThe current version is 1.8.1, which is ~25 years
    old.

    There's an upcoming new version which will introduce a number of new
    features (such as 64 bit integers, unicode support and more) that will
    be somewhat incompatible with databases running under version 1.8.1.
    Many of those are optional.

    To not cause too much disruption, I'd like to create two flavors: a
    default 'legacy compatible' flavor that is configured to behave like
    the 1.8.1 release and a 'modern' flavor that enables a number of the
    new features. This would create two binary packages, the default one
    being the automatic upgrade path when using binary packages, and the
    new available for admins that want to migrate their moo database to
    make use of the new features.

    However, I would also still provide the ability to manually configure
    the port and enable individual features.

    I think I can get what I want by defining options for all the features
    and then define OPTIONS_FILE differently for the two flavors as well as providing different OPTIONS_DEFAULT values for the flavors.

    I see other ports doing similar things, so it's not without precedent,
    but I'm curious whether that's the canonical way to go about it or
    whether there are other ways of going about this.

    Cheers,

    Koen
    Hi Koen,
    This sounds like a proper solution. When you put up a patch in bugzilla I'm able to review.
    As your name and .nl website hint on being Dutch I want to point (or invite) you to the https://bsdnl.nl/ group.
    Regards,
    Ronald.
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2