Date: Thu, 9 Apr 2026 11:37:05 +0300 From: Gleb Popov <arrowd@freebsd.org> To: Eygene Ryabinkin <rea@freebsd.org> Cc: Vladimir Druzenko <vvd@freebsd.org>, Charlie Li <vishwin@freebsd.org>, ports-committers <ports-committers@freebsd.org>, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org, Alexey Dokuchaev <danfe@freebsd.org> Subject: Re: git: ef9180aa8469 - main - science/py-scipy: update to 1.17.1 Message-ID: <CALH631nh=vEVBnWdb67cZ-qafCJ77%2BYng=_QWYGTbMy9N9F0Jg@mail.gmail.com> In-Reply-To: <j3uotvqupofbmnoxes75bhda74knuomx5hdv3acsspl6nfhyc2@dney653nqxyi> References: <CALH631kW-KxA2t6cTu8JY7ztV8cR1b2qYtDhcnuJwMWup0cGHg@mail.gmail.com> <CALH631mLkdvM1YxjcWNigRni3_DZFZhPGMTdK-_%2B%2BqBoTKNFcQ@mail.gmail.com> <j3uotvqupofbmnoxes75bhda74knuomx5hdv3acsspl6nfhyc2@dney653nqxyi>
index | next in thread | previous in thread | raw e-mail
On Tue, Apr 7, 2026 at 6:53 PM Eygene Ryabinkin <rea@freebsd.org> wrote: > > Historically, this is the other way around: ports framework allowed > to build in the system itself, but over the time (and accumulating > arguments like "library/package detection in autotools and others > pick stuff from the live system, so the virtual environment is the > /only?/ way to go") it shifted to your "is not supported". It is not mine. It is the reality. The amount of software is huge, thus the amount of concurrently installed packages on a given system grows as well. The diversity of installed packages also increases. Build systems become more and more complex. All this makes impossible to ensure reproducible builds in uncontrolled environments and it is unrealistic to require Ports committers to ensure that the port builds outside of Poudriere. Moreover, ensuring that the port builds outside of poudriere for one developer does not mean that someone else would not bump into problems. So we're back to "fix your problems on your own if you're building outside the jail. No one has the same env as you to be able to reproduce your issue. > > No, rpmbuild is the virtual environment (buildroot) maker And what does that entail? My point is that rpmbuild runs without the isolation, so the software's build system will look for deps from the host. Just like when you build a port with plain make. > > But I digress. The bottom line is that the only supported way to build packages > > for FreeBSD is Poudriere, so I'm asking for 100th time to stop grumbling on > > the ML about breakages that you've chosen to bump into. > > And there is another view on this: it is not "you've chosen to bump > into", but rather the user of FreeBSD (and, perhaps, the power > user?) who still remembers the "good old days of ports" (I am not > joking: port building used to be fun, at least for me; then, around > 2011 it started to be annoying with OPTIONS, especially the custom ones, > then /around 2020s? A bit earlier?/ it started to be an almost no-go > to build packages for the system inside the system itself when I needed > to support ~50-150 packages on each server), says "it is why I still use > and, perhaps, love FreeBSD for". Yes, I am very well aware of you old people, thanks for Russian Telegram channel. And yes, I personally don't care about problems you get yourself into because you choose to. Yet, > You really dare to drop such > users? I'm not dropping anyone. Building on host with make/portmaster/synth is still possible. I'm only saying that you should not expect a first-class support for that. I'm fine with accepting patches that improve QoL for people like you, though.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALH631nh=vEVBnWdb67cZ-qafCJ77%2BYng=_QWYGTbMy9N9F0Jg>