I wrote:
>
> > From: bugzilla-nore...@freebsd.org
> > Date: Tue, 03 May 2022 17:20:14 +
> > To: j...@berklix.com
> >
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263758
> >
> > Li-Wen Hsu changed:
> >
> >What|Removed |Added
> > -
04.05.2022 2:42, Ed Maste wrote:
> On Fri, 29 Apr 2022 at 14:43, Eugene Grosbein wrote:
>>
>> For example:
>>
>> if_em
>> https://cgit.freebsd.org/src/commit/?id=c0460cf2e42d2819c1f191a1d6e1b3dc0c7ea010
>> if_epair
>> https://cgit.freebsd.org/src/commit/?id=7a382e744b0b0ba9b51d
On Fri, 29 Apr 2022 at 14:43, Eugene Grosbein wrote:
>
> For example:
>
> if_em
> https://cgit.freebsd.org/src/commit/?id=c0460cf2e42d2819c1f191a1d6e1b3dc0c7ea010
> if_epair
> https://cgit.freebsd.org/src/commit/?id=7a382e744b0b0ba9b51dc34bfa0cd1515f744f25
> linuxkpi
> h
> From: bugzilla-nore...@freebsd.org
> Date: Tue, 03 May 2022 17:20:14 +
> To: j...@berklix.com
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263758
>
> Li-Wen Hsu changed:
>
>What|Removed |Added
> ---
Hi, Reference:
> From: Eugene Grosbein
> Date: Tue, 3 May 2022 22:13:26 +0700
Eugene Grosbein wrote:
> 03.05.2022 21:46, Julian H. Stacey wrote:
>
> > Hi, Reference:
> >> From: "Julian H. Stacey"
> >> Date: Fri, 29 Apr 2022 23:57:02 +0200
> >
> > "Juli
03.05.2022 21:46, Julian H. Stacey wrote:
> Hi, Reference:
>> From:"Julian H. Stacey"
>> Date:Fri, 29 Apr 2022 23:57:02 +0200
>
> "Julian H. Stacey" wrote:
>> Ed Maste wrote:
>>> On Thu, 28 Apr 2022 at 11:28, Julian H. Stacey wrote:
but that's crude. It
Hi, Reference:
> From: "Julian H. Stacey"
> Date: Fri, 29 Apr 2022 23:57:02 +0200
"Julian H. Stacey" wrote:
> Ed Maste wrote:
> > On Thu, 28 Apr 2022 at 11:28, Julian H. Stacey wrote:
> > >
> > > but that's crude. It's nice to be able to build most modules ready
> > > in case wan
Ed Maste wrote:
> On Thu, 28 Apr 2022 at 11:28, Julian H. Stacey 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
>
29.04.2022 21:49, Ed Maste wrote:
> On Thu, 28 Apr 2022 at 11:28, Julian H. Stacey 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 i
On Thu, 28 Apr 2022 at 11:28, Julian H. Stacey 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 sh
module(s) will break, such has been the way for years
with breaking modules.
The only current way round breaking modules is to use
.if defined(MODULES_OVERRIDE) && !defined(ALL_MODULES)
SUBDIR=${MODULES_OVERRIDE}
.else
but that's crude. It's nice to be abl
11 matches
Mail list logo
