From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] : How to add a path to environment variable ?
Date: Thu, 21 Jan 2021 22:43:38 +0100 [thread overview]
Message-ID: <20210121214338.GD2375@scaer> (raw)
In-Reply-To: <20210121204741.08247783@windsurf.home>
Thomas, Manu, All,
On 2021-01-21 20:47 +0100, Thomas Petazzoni spake thusly:
> On Thu, 21 Jan 2021 18:02:39 +0100
> manu f <e.fiancette@gmail.com> wrote:
> > Thanks for your suggestion!
> > in the last buildroot version, nodejs is deprecated!
> > So I use my own compiled version of nodejs.
>
> Deprecated ? We definitely still have a nodejs package, and it's not
> deprecated at all.
I think Manu meant that the version of nodejs we cary is depreceated.
Indeed, we still have nodejs 12.20.1, which is not the latest.
However, it is not deprecated. 12.x is in maintenance-only now, until
around May 2022, which means we cary a stable version, on which people
can be sure no API breakage will occur; only bug fixes and security
fixes will be applied (in practice, only security fixes).
The other LTS, 14.x, will continue to receive evolutions until Oct.
2021, after which it will enter maintainance-only mode. So it is
currently not as stable as 12.x.
15.s will not be an LTS, and will disapear around end os S1 2021.
16.x is not even released yet, and will be the next LTS.
So in the end, I would not qualify our version of being deprecated; it's
just not the latest LTS.
12.x is stable, and a good fit I believe for our next LTS.
Note: I am *not* arguing for having two versions of nodejs in the tree.
No, no, no! ;-]
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2021-01-21 21:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 15:32 [Buildroot] : How to add a path to environment variable ? manu f
2021-01-21 16:47 ` Thomas Petazzoni
2021-01-21 17:02 ` manu f
2021-01-21 19:47 ` Thomas Petazzoni
2021-01-21 21:43 ` Yann E. MORIN [this message]
2021-01-22 10:47 ` Peter Korsgaard
2021-01-22 11:22 ` manu f
2021-01-22 15:35 ` Peter Korsgaard
2021-01-22 15:45 ` manu f
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210121214338.GD2375@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.