Date: Thu, 24 Aug 2023 11:01:40 +0300 From: Gleb Popov <arrowd@freebsd.org> To: Theron <theron.tarigo@gmail.com> Cc: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Getting lib32 porting effort unstuck Message-ID: <CALH631mJgCx1Su448YWSbysVXLSVbiOU-yTviKyGd0o58d9J5g@mail.gmail.com> In-Reply-To: <e0128442-1b71-bf0f-6fa4-8db9d4521dc2@gmail.com> References: <1394819d-69c2-2724-d3cb-38b82046cb2b@gmail.com> <CALH631n66gi4r8FOWhHH%2BTQuw5X384MZ%2BXPuYoLggaCMtRoEhg@mail.gmail.com> <e0128442-1b71-bf0f-6fa4-8db9d4521dc2@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 23, 2023 at 11:39=E2=80=AFPM Theron <theron.tarigo@gmail.com> w= rote: > > On 8/23/23 15:58, Gleb Popov wrote: > > If the 32bit library set doesn't need to be updated frequently one way > > to do this is repackaging. > > Write a script that builds required libraries in the 32-bit Poudriere > > jail (possibly with LOCALBASE=3D/usr/local32 or something) and then > > repackage resulting .pkg files into a single one. Then write a > > NO_BUILD port that would install this huge .pkg > That's the system that was previously in place. The wine port > maintainers at the time also operated a build server for this purpose, > which served as the master site for the wine port's lib32 binaries. > This had to be abandoned at least once as it was not always maintained. Why not revive this approach? It doesn't seem like too much maintenance wor= k.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALH631mJgCx1Su448YWSbysVXLSVbiOU-yTviKyGd0o58d9J5g>