Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 10 May 2021 22:05:13 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 255578] net/isboot-kmod: Update to 0.2.14
Message-ID:  <bug-255578-7788-TGLI9N3Cn0@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-255578-7788@https.bugs.freebsd.org/bugzilla/>
References:  <bug-255578-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255578

--- Comment #2 from John Nielsen <john@jnielsen.net> ---
(In reply to Li-Wen Hsu from comment #1)
I don't know how hard it would be to keep/restore support for 11 either. I
didn't worry too much about it because the EoL date is not far off and I'm =
not
sure if or how well the old port works on 11. I maintain the port because I
appreciate its functionality but I am not a primary developer of the code.
There have not been any updates (or responses to my inquiries) from the
original developer in some years. The patch for 0.2.14 landed in my inbox f=
rom
Michael Zoon at XigmaNAS. He says that Daisuke Aoyama (the original author)=
 is
one of the devs on his project.

I created the github repo as a way to bring sanity to managing the patches =
and
to have a place to download the updated tarballs from.

AFAIK 0.2.14 does not have any new functionality, the updates just allow it=
 to
build on 12 and 13. If 0.2.13 is functional on FreeBSD 11 I'm open to keepi=
ng
it around as a deprecated option.

I have not done any (build or other) testing on non-x86 platforms.

I would love for this code to be merged in to FreeBSD's src tree, I'm surpr=
ised
it or something like it is not already in base.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255578-7788-TGLI9N3Cn0>