From nobody Fri May 26 15:13:31 2023 X-Original-To: ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QST2Y3RV9z4Wrc3 for ; Fri, 26 May 2023 15:13:25 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4QST2Y1kpVz3sDH; Fri, 26 May 2023 15:13:25 +0000 (UTC) (envelope-from pi@freebsd.org) Authentication-Results: mx1.freebsd.org; none Received: from pi by fc.opsec.eu with local (Exim 4.96 (FreeBSD)) (envelope-from ) id 1q2Z8F-000JqX-2h; Fri, 26 May 2023 17:13:31 +0200 Date: Fri, 26 May 2023 17:13:31 +0200 From: Kurt Jaeger To: Guido Falsi Cc: "ports@FreeBSD.org Ports" , Po-Chuan Hsieh Subject: Re: graphics/podofo: 0.10.x requirement Message-ID: References: <3e5e10a3-75e7-795e-edbf-378bcb4999a4@FreeBSD.org> List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3e5e10a3-75e7-795e-edbf-378bcb4999a4@FreeBSD.org> X-Rspamd-Queue-Id: 4QST2Y1kpVz3sDH X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N > Hi, > > As the maintainer of the calibre port, while trying to update to 6.18.x > I've discovered that now calibre requires the new API/ABI incompatible > podofo 0.10 version. > > I also guess that other ports will also grow such requirements in the > future. > > So my question, both general and to the sunpoet as podofo maintainer, > is, how should we address this? > > Also, is this already being addressed, maybe? > > We can't simply update graphics/podofo, obviously (all dependent ports > would brake). > > Plan 1 - My first idea is creating a graphics/podofo10 port that can be > installed in parallel with graphics/podofo (by changing the name of > every file installed that conflicts), so that ports moving to the newer > library can be patched to use the newer one. That's how it is done for other dependencies in other ports sometimes. netbox and gitlab often have such cases. > plan 2 - Another option is doing the same as above, but my updating > podofo to the latest version and moving old 0.9.x to a graphics/podofo09 > (or whatever) port, updating all dependencies to use the older port for now. Also fine. -- pi@FreeBSD.org +49 171 3101372 Now what ?