Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Geoff Levand <geoff@infradead.org>,
	Anisse Astier <anisse@astier.eu>,
	Angelo Compagnucci <angelo.compagnucci@gmail.com>,
	Marcin Niestroj <m.niestroj@grinn-global.com>,
	Buildroot Mailing List <buildroot@buildroot.org>,
	Romain Naour <romain.naour@gmail.com>,
	Fabio Estevam <festevam@gmail.com>,
	Thomas Perale <thomas.perale@mind.be>,
	Thomas Perale <thomas.perale@essensium.com>
Subject: Re: [Buildroot] [PATCH 1/4] package/goc: new virtual package
Date: Mon, 17 Oct 2022 20:48:19 +0200	[thread overview]
Message-ID: <20221017204819.47cb4078@windsurf> (raw)
In-Reply-To: <20221017175500.GB3666@scaer>

On Mon, 17 Oct 2022 19:55:00 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> In fact, we want to have a similar implementation for rust, go, nodejs,
> so (without looking at the details of this series), I guess Thomas
> Perale took the same approach as the existing rust situation, like
> Thomas Petazzoni did in the recent host-nodejs series:
> 
>     https://patchwork.ozlabs.org/project/buildroot/list/?series=319967

Yes and no, because Thomas Perale changed all packages using Go to use
host-goc instead of host-go, while my series keeps host-nodejs but
changes it from host-generic-package to host-virtual-package.

Also, I'd like to recap the naming we have:

 - Rust (existing)
   virtual package: 		host-rustc
   pre-compiled package:   	host-rust-bin
   from source package:         host-rust

 - NodeJS (proposed by me)
   virtual package:             host-nodejs
   pre-compiled package:        host-nodejs-bin
   from source package:         host-nodejs-src

   The odd thing here being that host-nodejs is a virtual package, but
   nodejs is a regular package building NodeJS from source for the
   target.

 - Go (proposed by Thomas Perale)
   virtual package:		host-goc
   pre-compiled package:        host-go-bin
   from source package:         host-go

So Thomas aligned on the naming used in the Rust world. I must say I do
have a preference for the naming I have chosen for NodeJS, which IMO is
clearer.

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-10-17 18:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221017142849.41399-1-thomas.perale@mind.be>
     [not found] ` <20221017142849.41399-4-thomas.perale@mind.be>
2022-10-17 16:05   ` [Buildroot] [PATCH 3/4] package/go-bin: new package Christian Stewart via buildroot
2022-10-17 18:03     ` Yann E. MORIN
2022-10-17 18:42       ` Thomas Petazzoni via buildroot
2022-10-17 18:52         ` Christian Stewart via buildroot
     [not found] ` <20221017142849.41399-2-thomas.perale@mind.be>
2022-10-17 16:06   ` [Buildroot] [PATCH 1/4] package/goc: new virtual package Christian Stewart via buildroot
2022-10-17 17:55     ` Yann E. MORIN
2022-10-17 18:10       ` Christian Stewart via buildroot
2022-10-17 18:30         ` Thomas Perale via buildroot
2022-10-17 18:44         ` Yann E. MORIN
2022-10-17 18:51           ` Christian Stewart via buildroot
2022-10-18  8:03             ` Thomas Perale via buildroot
2022-10-17 18:48       ` Thomas Petazzoni via buildroot [this message]
2022-10-17 15:17 [Buildroot] [PATCH 0/4] Add support for using a pre-compiled Go compiler Thomas Perale via buildroot
2022-10-17 15:17 ` [Buildroot] [PATCH 1/4] package/goc: new virtual package Thomas Perale via buildroot

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=20221017204819.47cb4078@windsurf \
    --to=buildroot@buildroot.org \
    --cc=angelo.compagnucci@gmail.com \
    --cc=anisse@astier.eu \
    --cc=festevam@gmail.com \
    --cc=geoff@infradead.org \
    --cc=m.niestroj@grinn-global.com \
    --cc=romain.naour@gmail.com \
    --cc=thomas.perale@essensium.com \
    --cc=thomas.perale@mind.be \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox