All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Christian Stewart <christian@paral.in>
Cc: Geoff Levand <geoff@infradead.org>,
	Anisse Astier <anisse@astier.eu>,
	Angelo Compagnucci <angelo.compagnucci@gmail.com>,
	Marcin Niestroj <m.niestroj@grinn-global.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.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 19:55:00 +0200	[thread overview]
Message-ID: <20221017175500.GB3666@scaer> (raw)
In-Reply-To: <CA+h8R2qwa-bzHzogQoVRubbapo1EwKmzyPML_hJQww144DWv6g@mail.gmail.com>

Christian, All,

On 2022-10-17 09:06 -0700, Christian Stewart spake thusly:
> On Mon, Oct 17, 2022, 7:29 AM Thomas Perale < [1]thomas.perale@essensium.com> wrote:
>   This virtual package implement the already existing go compiler compiled
>   from source and shows it on the host package menu.
>   The usage of a virtual package on top of the go compiler enable the
>   supports of for multiple providers for the Go compiler.
> Is it not possible to continue using the existing host-go target and
> simply add a parameter which enables downloading the precompiled
> version instead?
> Rather than add a new package.

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

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.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-10-17 17:55 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 [this message]
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
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=20221017175500.GB3666@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=angelo.compagnucci@gmail.com \
    --cc=anisse@astier.eu \
    --cc=buildroot@buildroot.org \
    --cc=christian@paral.in \
    --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 \
    /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.