[Slackbuilds-users] Upstream LTS Releases & Possibility of New Node.js 18.x SlackBuild

[Willy Sudiarto Raharjo]

> Hello Fellow Slackers,
> 
>          What is the SlackBuild typical practice
>    regarding packages that have multiple concurrently
>    supported upstream releases?  The Node.js project,
>    for example, maintains a current version, and
>    multiple LTS versions.
> 
>          SlackBuilds currently packages only the
>    latest LTS version of Node.js.  I find myself
>    deploying previous LTS for some production
>    projects (previous LTS is still maintained
>    upstream), or using newer non-LTS versions for
>    development of new projects.
> 
>          I'm interested in maintaining a SlackBuild
>    of the Node.js previous LTS (the 18.x.x series),
>    which is still supported upstream, and is used in
>    some projects I'm responsible for.
> 
>          Inspired by the likes of zulu-openjdk21, and
>    zulu-openjdk17, etc. maybe a nodejs18 package
>    would be acceptable?

yes, it's possible to do that
i was also planning to do the same with postgresql since they have 
annual release cycle

-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240928/fe5a73ed/attachment.asc>