Date: Thu, 9 Apr 2026 23:01:06 +0300 From: Gleb Popov <arrowd@freebsd.org> To: Yuri Victorovich <yuri@freebsd.org> Cc: Eygene Ryabinkin <rea@freebsd.org>, ports-committers <ports-committers@freebsd.org>, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: 097b8e780932 - main - misc/ollama: Fix package on non-x86 architectures Message-ID: <CALH631krhHTOaH4osZN7Xniq2NCp2mFHMXU5Wsk-hV6bqH_z9w@mail.gmail.com> In-Reply-To: <462c9475-d379-4ecb-aca1-6331e19e7266@freebsd.org> References: <69ce1085.20cac.772d7539@gitrepo.freebsd.org> <CALH631mHaMRmvmugX90u-ep5D73=QqY0S_9MiZxwk8zX1M3VcQ@mail.gmail.com> <2995c1f6-79b2-4119-9168-09df9e24736a@freebsd.org> <CALH631k7WN7pVe2aE6PzPQa0YxPMbgPQagvqO%2Bpx6VGcTBRZEw@mail.gmail.com> <wyvdnktd2nwj4zx4vvwmectw3xkj5l4hapkycjoskhrjpyghzp@edrzpm2ul5tx> <CALH631=A73KE7-y_405Y4jxtWERsFcQxPs5NkyS-KuedsgiWtg@mail.gmail.com> <462c9475-d379-4ecb-aca1-6331e19e7266@freebsd.org>
index | next in thread | previous in thread | raw e-mail
On Thu, Apr 9, 2026 at 10:01 PM Yuri Victorovich <yuri@freebsd.org> wrote: > > On 4/9/26 00:48, Gleb Popov wrote: > > Yuri playing the lone wolf is what bothers me. There were multiple > > complaints for his actions from multiple contributors including > > portmgr, but yuri just keeps doing his own thing. > > > Gleb, > > > > When did I ignore complaints? Can you provide examples? I don't believe that any of my arguments would persuade you. But since you're asking: 1. https://lists.freebsd.org/archives/dev-commits-ports-all/2026-April/197895.html I asked you the same 2 years ago when I was enrolled into the portmgr-lurker program. I explained to you that your ports contribute to other committer's workload when they are doing sweeping changes. I again bumped into this myself just recently when preparing Ports for Flang. Most of Fortran problematic ports were yours, a highly specialized software with weird build systems, which I doubt have any consumers amongst FreeBSD users. Speaking of which, 2. I already asked you to perform your maintainer duties for these ports: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289342 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289570 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289582 But yeah, those are non-trivial and it is much easier to get back to porting Python modules or update a git-versioned port every time upstream pushes a new commit. 3. https://lists.freebsd.org/archives/dev-commits-ports-all/2025-October/179707.html Is this enough for you, or should I spend even more of my time searching the archives, instead of doing a useful work for FreeBSD? > In this particular case I disagree with suggestions to use ${ARCH} > because of the reasons I explained earlier. Those reasons are invalid, because you don't need to include anything but bsd.port.mk at the end. vvd gave you an example how to do it with plain make vars.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALH631krhHTOaH4osZN7Xniq2NCp2mFHMXU5Wsk-hV6bqH_z9w>