Date: Mon, 25 Sep 2023 03:15:46 +0200 From: Robert Clausecker <fuz@fuz.su> To: qroxana <qroxana@protonmail.com> Cc: "freebsd-ports@FreeBSD.org" <freebsd-ports@freebsd.org> Subject: Re: Go and Rust ports PORTREVISION bump up question Message-ID: <ZRDfQte5PO7tEtTA@fuz.su> In-Reply-To: <5JtQsYbjhobDiFATZAEsiLcgrBdLmMgbhZR3xejYloFJj_U6TZvi8Rq5Qbg9HFTyHTWdLd_ZyS_6YJOAF0XKfH3zI_evvXRtD06SJXmq1xA=@protonmail.com> References: <5JtQsYbjhobDiFATZAEsiLcgrBdLmMgbhZR3xejYloFJj_U6TZvi8Rq5Qbg9HFTyHTWdLd_ZyS_6YJOAF0XKfH3zI_evvXRtD06SJXmq1xA=@protonmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi qroxana, Go and rust ports statically link parts of the runtime provided by the toolchain ports, but do not have a LIB_DEPENDS on it. PORTREVISION is bumped on toolchain update so the ports get rebuilt with the new version of the toolchain and receive whatever standard library patches the update comes with. Yours, Robert Clausecker Am Mon, Sep 25, 2023 at 01:07:52AM +0000 schrieb qroxana: > Just curious, what is reason for bumping up the PORTREVISION of > the GO and Rust ports, after lang/go or lang/rust is updated? > > Thanks. -- () ascii ribbon campaign - for an 8-bit clean world /\ - against html email - against proprietary attachments
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZRDfQte5PO7tEtTA>