From nobody Fri May 26 15:18:36 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 4QST8W4D4dz4WrkB for ; Fri, 26 May 2023 15:18:35 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QST8W3g58z3td6; Fri, 26 May 2023 15:18:35 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685114315; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=YxWraCv0Au5+4tWInKP0QljBD2ZRx054DBYXkGi6pIk=; b=PsnqS9CI+R8t8bDcJzchRzQBCJXtkqe76Dcjk+fpNOIl/s9my1k7WIHEHFL4yoI3HIcsrq 2KZsoAAJUnU8A/WvPE3MfjRdGHjerTnSWTt8+qP95v/Y3Uj2+IN3gSzoRWMH2eUjZLAV2L ts9jax4FP9+kCyBpMzrQ0JSQG5+Oj1J88tZHBW7F1NoAMUvCg3iRZCKLDCg9tkSv7j9IhN DN0AS1hSzqXVP7e/5VuAUdM/iEdlSlrd0mxFlnCUjafwU5cM+1XdMzHPaQVs15LpkMA3Y3 dUZUkqUtf9jyHDOjrBFa01yh9Mb3KFYpIUtbV5y4Qin+TL2KzN4bVhMvEdsi9w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685114315; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=YxWraCv0Au5+4tWInKP0QljBD2ZRx054DBYXkGi6pIk=; b=ccdKcUHUvRXcEQqwRGs1sUwqirR4k6IJQSvoGnadcx0qhAvJxw2aqYn3s4Sd0EWTqnAjLb ZgrzkN1mqP8cu0Exun/E7ag8yGUay8aLUhjVcQ8wQs36UiqRa8u3s0in0bg1sKxzQTuCbh fgKLBNp/1+tPahUaboQ3H8fDm/vKYfCG2vO117HrSvCFHiTsvfcbH+MHbdVi+OgHOX6EUb 6CJcSj7ESkfupULRpLIpdBfHRb/FkdbPriE/DYvEQ4l0D28q/uZzZuJuGg4pcqQ8mJzfdp 1xXLyUqRKQpLOwLGMrzdUUc5A11X5b46ySbNs+lrZ1ZfYxkNBfegnM9SSsI2zg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1685114315; a=rsa-sha256; cv=none; b=pLeJ3LzWQfPZ6UQiepDNnknAz3NFkC5e2eWH+3xIJRzbgmEzy1M70/eK6OZ6EwYcRo++GM 1IMlIiECKn+6WfisTh4jH372Ogb0viJmZi5nhz5oVkfnoxcW5BjJnL9FbJG6Vsz6u3+jRd RvHPPcqdxidkOvfkAkRumigtPxkA8S1jQ2r4dXr3iwt8CFRzu7uSQjHNeWewfqqY2KH8aj GUpXgvFoomLX84WrS20+fuMrQ8fxQyYg4Bd0o25bttFEdynT2glCY/KsKs203RcTiU18eR efV8UyOMvC1JGaCiN4/qsDHluzB1VM+5cQKTSdQCLQsAfcmhU+y3t+M2IGTxXg== Received: from [IPV6:2a01:e11:2002:4280::13:1] (unknown [IPv6:2a01:e11:2002:4280::13:1]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) (Authenticated sender: madpilot/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QST8V6ZV7z132T; Fri, 26 May 2023 15:18:34 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Message-ID: <061bc038-bf20-ad47-f571-eb153ccce092@FreeBSD.org> Date: Fri, 26 May 2023 17:18:36 +0200 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 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.11.1 Subject: Re: graphics/podofo: 0.10.x requirement Content-Language: en-US To: Kurt Jaeger Cc: "ports@FreeBSD.org Ports" , Po-Chuan Hsieh References: <3e5e10a3-75e7-795e-edbf-378bcb4999a4@FreeBSD.org> From: Guido Falsi In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-ThisMailContainsUnwantedMimeParts: N On 26/05/23 17:13, Kurt Jaeger wrote: >> 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. > Suspected that, I'm also waiting for sunpoet (as podofo maintainer) opinion. Maybe he also already has a plan or is working on something that I don't know about. -- Guido Falsi