Date: Fri, 29 Apr 2022 10:49:04 -0400 From: Ed Maste <emaste@freebsd.org> To: "Julian H. Stacey" <jhs@berklix.com> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: breaking modules Message-ID: <CAPyFy2BAazqi9vqjWwM94qEeF%2Bh5MBTTy94PbbNH-N-5w4_9_w@mail.gmail.com> In-Reply-To: <202204281527.23SFRbKU090763@fire.js.berklix.net> References: <202204281527.23SFRbKU090763@fire.js.berklix.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 28 Apr 2022 at 11:28, Julian H. Stacey <jhs@berklix.com> wrote: > > but that's crude. It's nice to be able to build most modules ready > in case wanted later, so how about a DUDS env. mechanism like ports/ ? I'd rather not add additional complexity to our build infrastructure to address a situation that shouldn't exist. Modules should build & function on an ongoing basis (and, I believe they generally do). CI doesn't report any issues on either stable branch or main at present.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2BAazqi9vqjWwM94qEeF%2Bh5MBTTy94PbbNH-N-5w4_9_w>