Re: lang/rust: roadmap for using SYSTEM_VERSION

2024-01-01 Thread Theo Buehler
On Mon, Jan 01, 2024 at 07:28:17AM +0100, Sebastien Marie wrote: > Hi, > > With the hint from espie@, it is possible to have a proper inclusion of > lang/rust module from devel/cargo module. So it is possible to have a > more simple usage of devel/cargo. > > I would introduce a new lang/rust modu

Re: lang/rust: roadmap for using SYSTEM_VERSION

2023-12-31 Thread Sebastien Marie
Hi, With the hint from espie@, it is possible to have a proper inclusion of lang/rust module from devel/cargo module. So it is possible to have a more simple usage of devel/cargo. I would introduce a new lang/rust module (with just SYSTEM_VERSION-rust, BUILD_DEPENDS+=lang/rust, and MODRUST_WANTLI

Re: lang/rust: roadmap for using SYSTEM_VERSION

2023-12-31 Thread Marc Espie
On Sun, Dec 31, 2023 at 12:26:28PM +0100, Sebastien Marie wrote: > Theo Buehler writes: > > > On Sat, Dec 30, 2023 at 07:32:18PM +0100, Sebastien Marie wrote: > > > > The outlined procedure makes sense to me and I like the approach, but I > > am a bit worried that it makes it harder for people to

Re: lang/rust: roadmap for using SYSTEM_VERSION

2023-12-31 Thread Klemens Nanni
On Sun, Dec 31, 2023 at 12:26:28PM +0100, Sebastien Marie wrote: > initially, I tried to hide the "lang/rust" module under "devel/cargo" > module (and have devel/cargo to sets MODULES+=lang/rust), but > arch-defines.mk is included before MODULES processing, which means that > the test ${MODULES:Mla

Re: lang/rust: roadmap for using SYSTEM_VERSION

2023-12-31 Thread Theo Buehler
> Regarding MODCARGO_WANTLIB to MODRUST_WANTLIB transition, it might be > possible to define the first using the second (MODCARGO_WANTLIB = > ${MODRUST_WANTLIB}). > But I am unsure if it would really help or not. I am not convinced either. If it is possible, it would avoid a bit of churn in your

Re: lang/rust: roadmap for using SYSTEM_VERSION

2023-12-31 Thread Sebastien Marie
Theo Buehler writes: > On Sat, Dec 30, 2023 at 07:32:18PM +0100, Sebastien Marie wrote: > > The outlined procedure makes sense to me and I like the approach, but I > am a bit worried that it makes it harder for people to write Rust ports > using the devel/cargo module, which is already tricky. >

Re: lang/rust: roadmap for using SYSTEM_VERSION

2023-12-31 Thread Theo Buehler
On Sat, Dec 30, 2023 at 07:32:18PM +0100, Sebastien Marie wrote: > Hi, > > We need a way to bump all ports built using lang/rust when the port is > updated (compiler change or rust stdlib changes). > > Currently, lang/go is using SYSTEM_VERSION-go variable for that, so I > intent to copy the meca

lang/rust: roadmap for using SYSTEM_VERSION

2023-12-30 Thread Sebastien Marie
Hi, We need a way to bump all ports built using lang/rust when the port is updated (compiler change or rust stdlib changes). Currently, lang/go is using SYSTEM_VERSION-go variable for that, so I intent to copy the mecanism for rustc. I can't simply use devel/cargo module for that: some (usually