Date: Tue, 11 Jun 2024 04:41:47 +0200 From: Jan Beich <jbeich@FreeBSD.org> To: Alexey Dokuchaev <danfe@freebsd.org> Cc: ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: 29edf60ed922 - main - sysutils/ncdu2: unbreak build after 7fa85e6a3844 Message-ID: <a5js-b3pw-wny@FreeBSD.org> In-Reply-To: <Zme2OHq-g8fItpTz@FreeBSD.org> (Alexey Dokuchaev's message of "Tue, 11 Jun 2024 02:28:08 %2B0000") References: <202406102304.45AN4Vp1016457@gitrepo.freebsd.org> <bk48-mllz-wny@FreeBSD.org> <Zme2OHq-g8fItpTz@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
Alexey Dokuchaev <danfe@freebsd.org> writes: > On Tue, Jun 11, 2024 at 01:19:52AM +0200, Jan Beich wrote: > >> Jan Beich <jbeich@FreeBSD.org> writes: >> > -BUILD_DEPENDS= zig>=0.12<0.12_99:lang/zig >> > +BUILD_DEPENDS= zig>=0.12.1<0.12.1_99:lang/zig >> >> Obviously under "portmgr blanket". The maintainer wants to personally >> validate every lang/zig update[1] but also benefit from changes made by >> others - "have a cake and eat it, too". >> >> I should probably mark it BROKEN the next time instead of wasting time. > > It should be just zig:lang/zig, period. Depending on the package version > is fragile and clearly asking for trouble vs. depending on the file which > would always work and DTRT. How would it work when multiple lang/zig* ports install "zig" binary? According to semantic versioning before 1.0 projects are allowed to break backward compatibility any time. Usually, this is done during "minor" while "patch" updates are reserved for compatible bug fixes. For example, lang/zig hasn't reached 1.0 unlike lang/rust.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a5js-b3pw-wny>