Date: Sat, 13 Jan 2024 19:43:32 +0100 From: Daniel Engberg <daniel.engberg.lists@pyret.net> To: Charlie Li <vishwin@freebsd.org> Cc: Gleb Popov <arrowd@freebsd.org>, ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: 25e6f68a6661 - main - textproc/libxml2: Update to 2.11.6 Message-ID: <30d803b8ab6713c88aa8fe2c0e516e51@mail.infomaniak.com> In-Reply-To: <d9314eaa-4629-49d4-8929-ba7b0551762a@freebsd.org> References: <202401121705.40CH5JhG014492@gitrepo.freebsd.org> <ZaIcEvYZ2Yq_jW9Z@FreeBSD.org> <CALH631=meexWeEvPY4dBsVviAEms9OfcmKTk-YHGfw4fHJCzSw@mail.gmail.com> <a228d839c5a29d9991b72f1e0664da04@mail.infomaniak.com> <02ebab1b-a763-45e4-9380-0d82c83c22a4@freebsd.org> <CALH631keLuwEchvHA8OWuHy_LiWsodJi8VL5NN-L5p1WYsKGwA@mail.gmail.com> <d9314eaa-4629-49d4-8929-ba7b0551762a@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--_=_swift_1705171412_c086a9241248ee049129b2428ecf7797_=_ Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2024-01-13T18:46:34.000+01:00, Charlie Li <vishwin@freebsd.org> wrote:= >=C2=A0Gleb=C2=A0Popov=C2=A0wrote: >>=C2=A0=C2=A0On=C2=A0Sat,=C2= =A0Jan=C2=A013,=C2=A02024=C2=A0at=C2=A04:37=C2=A0PM=C2=A0Charlie=C2=A0Li= =C2=A0<vishwin@freebsd.org> >>=C2=A0=C2=A0wrote: >>=C2=A0=C2=A0 >>>= =C2=A0=C2=A0=C2=A0Until=C2=A0upstream=C2=A0specifically=C2=A0declares=C2= =A0and=C2=A0recommends=C2=A0CMake=C2=A0as >>>=C2=A0=C2=A0=C2=A0ready= =C2=A0for >>>=C2=A0=C2=A0=C2=A0 >>>=C2=A0=C2=A0=C2=A0=C2=A0Unix-like= =C2=A0systems=C2=A0in=C2=A0at=C2=A0least=C2=A0their=C2=A0documentation,= =C2=A0nothing=C2=A0else >>>=C2=A0=C2=A0=C2=A0is=C2=A0relevant. >>=C2= =A0=C2=A0 >>=C2=A0=C2=A0=C2=A0What=C2=A0makes=C2=A0you=C2=A0so=C2=A0categ= orical=C2=A0about=C2=A0it?=C2=A0Recommendations=C2=A0are, >>=C2=A0=C2= =A0well, >>=C2=A0=C2=A0 >>=C2=A0=C2=A0=C2=A0recommendations.=C2=A0The= =C2=A0upstream=C2=A0might=C2=A0even=C2=A0recommend=C2=A0nothing=C2=A0but = >>=C2=A0=C2=A0Linux. >>=C2=A0=C2=A0 >>=C2=A0=C2=A0=C2=A0Should=C2=A0we= =C2=A0not=C2=A0port=C2=A0such=C2=A0software=C2=A0then? >=C2=A0 >=C2= =A0=C2=A0The=C2=A0Build=C2=A0Instructions=C2=A0section=C2=A0of=C2=A0the= =C2=A0README=C2=A0specifically=C2=A0states=C2=A0 >=C2=A0 >=C2=A0"Autoto= ols=C2=A0(for=C2=A0POSIX=C2=A0systems=C2=A0like=C2=A0Linux,=C2=A0BSD,=C2= =A0macOS)",=C2=A0even=C2=A0in=C2=A0the=C2=A0 >=C2=A0 >=C2=A0latest= =C2=A0trunk.=C2=A0CMake=C2=A0was=C2=A0originally=C2=A0added=C2=A0mainly= =C2=A0for=C2=A0Windows=C2=A0support. >=C2=A0 >=C2=A0 >=C2=A0Their= =C2=A0CMake=C2=A0support=C2=A0on=C2=A0platforms=C2=A0like=C2=A0ours=C2= =A0still=C2=A0has=C2=A0an=C2=A0outstanding >=C2=A0bug=C2=A0 >=C2=A0 >= =C2=A0pertaining=C2=A0to=C2=A0dependency=C2=A0resolution,=C2=A0which=C2= =A0at=C2=A0least=C2=A0I=C2=A0consider=C2=A0a=C2=A0 >=C2=A0 >=C2=A0shows= topper.=C2=A0While=C2=A0upstream=C2=A0have=C2=A0been=C2=A0accepting=C2= =A0and=C2=A0responsive=C2=A0to >=C2=A0any=C2=A0 >=C2=A0 >=C2=A0and= =C2=A0all=C2=A0improvements=C2=A0to=C2=A0their=C2=A0CMake=C2=A0support,= =C2=A0that=C2=A0is=C2=A0irrelevant >=C2=A0until=C2=A0 >=C2=A0 >=C2= =A0they=C2=A0explicitly=C2=A0bless=C2=A0it=C2=A0as=C2=A0an=C2=A0equal=C2= =A0to=C2=A0autotools.=C2=A0(Not=C2=A0to=C2=A0say >=C2=A0autotools=C2= =A0 >=C2=A0 >=C2=A0is=C2=A0perfect=C2=A0either,=C2=A0far=C2=A0from= =C2=A0it) >=C2=A0 >=C2=A0Personally,=C2=A0between=C2=A0the=C2=A0two= =C2=A0choices=C2=A0here,=C2=A0I=C2=A0prefer=C2=A0CMake.=C2=A0But >=C2= =A0personal=C2=A0 >=C2=A0 >=C2=A0preferences=C2=A0are=C2=A0irrelevant= =C2=A0wrt=C2=A0liability=C2=A0and=C2=A0support=C2=A0issues. >=C2=A0 >= =C2=A0--=C2=A0 >=C2=A0 >=C2=A0Charlie=C2=A0Li >=C2=A0 >=C2=A0...nop= e,=C2=A0still=C2=A0don't=C2=A0have=C2=A0an=C2=A0exit=C2=A0line. Hi, = That's a bit contractionary? We upstream patches, community and others= also do and yet there's a "support issue" despite autotools is "far fr= om it" (perfect)? Why not embrace instead of obstructing? Please keep in = mind ports is a joint / community effort which is why we have groups, gui= delines etc and for custom trees there's overlay support for who want or = need to diverge. Best regards, Daniel --_=_swift_1705171412_c086a9241248ee049129b2428ecf7797_=_ Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <div>On 2024-01-13T18:46:34.000+01:00, Charlie Li <vishwin@freebsd.org&g= t; wrote:<br></div><div class=3D"ik_mail_quote answerContentMessage"><block= quote class=3D"ws-ng-quote"><pre style=3D"white-space: normal;"><div>Gleb P= opov wrote:<br></div><blockquote class=3D"ws-ng-quote"><div> On Sat, Jan 1= 3, 2024 at 4:37 PM Charlie Li <<a class=3D"defaultMailLink" href=3D"mail= to:vishwin@freebsd.org">vishwin@freebsd.org</a>> wrote:<br></div><blockq= uote class=3D"ws-ng-quote"><div> <br></div><div> Until upstream specificall= y declares and recommends CMake as ready for<br></div><div> Unix-like syste= ms in at least their documentation, nothing else is relevant.<br></div></bl= ockquote><div> <br></div><div> What makes you so categorical about it? Rec= ommendations are, well,<br></div><div> recommendations. The upstream might = even recommend nothing but Linux.<br></div><div> Should we not port such so= ftware then?<br></div></blockquote><div> The Build Instructions section of = the README specifically states <br></div><div>"Autotools (for POSIX systems= like Linux, BSD, macOS)", even in the <br></div><div>latest trunk. CMake w= as originally added mainly for Windows support. <br></div><div>Their CMake = support on platforms like ours still has an outstanding bug <br></div><div>= pertaining to dependency resolution, which at least I consider a <br></div>= <div>showstopper. While upstream have been accepting and responsive to any = <br></div><div>and all improvements to their CMake support, that is irrelev= ant until <br></div><div>they explicitly bless it as an equal to autotools.= (Not to say autotools <br></div><div>is perfect either, far from it)<br></= div><div><br></div><div>Personally, between the two choices here, I prefer = CMake. But personal <br></div><div>preferences are irrelevant wrt liability= and support issues.<br></div><div><br></div><div>-- <br></div><div>Charlie= Li<br></div><div>...nope, still don't have an exit line.<br></div></pre></= blockquote></div><div>Hi,<br></div><div><br></div><div>That's a bit contrac= tionary? We upstream patches, community and others also do and yet there's = a "support issue" despite autotools is "far from it" (perfect)? Why not emb= race instead of obstructing? Please keep in mind ports is a joint / communi= ty effort which is why we have groups, guidelines etc and for custom trees = there's overlay support for who want or need to diverge.<br></div><div><br>= </div><div>Best regards,<br></div><div>Daniel<br></div> --_=_swift_1705171412_c086a9241248ee049129b2428ecf7797_=_--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?30d803b8ab6713c88aa8fe2c0e516e51>