From nobody Sat May 27 11:24:42 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 4QSzww6Km4z4Wtvd for ; Sat, 27 May 2023 11:25:20 +0000 (UTC) (envelope-from sunpoet@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 4QSzww5ZS5z3xXP for ; Sat, 27 May 2023 11:25:20 +0000 (UTC) (envelope-from sunpoet@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685186720; 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: in-reply-to:in-reply-to:references:references; bh=XNdxsB0fSazzo8a558wf6NzRkSoRIlqbs0JOyv7de8s=; b=M7IlIXRpO/QHp/KgXxslBE6Knpfv1AH4mtGJrWIC3P3k92qhS917Z9penrjnDFltw5DcC1 AoG3CWGFJ8mYXovK6OJFqu7AYBsQAYL8uv+GCC71NaUzAeY89p8zrufRJQ684sDg4ssa5C yWSBE8b1kV/qkITjz+p6IomyBSLZ9YkXKeo9JPPtn2jkko1xML4HJHwbGuly6jfTu6jWIV fHQSHQlS7VK7FKfp+UZ3RZXNStouG6CHpDldy27N2yFvDkMbYfaAwmgypn6DawDLnGI1wH QbNwhxTvAudM6nkjmSLOS5LwuVXvW2cz8w1xsZBdvQwYC+rTNUuKr7rmYzMiHw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1685186720; 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: in-reply-to:in-reply-to:references:references; bh=XNdxsB0fSazzo8a558wf6NzRkSoRIlqbs0JOyv7de8s=; b=t9t2jKlY8S6LRu3z3gWAXwd4OubzlTS0SdvWjK5VYOBpqnTM63S0rfJAf0pdnqIOVUToFc W/fnSxPY0VCcapdFICWXO3Gt+OBENmdKQVV+Mppa/MntjCSu20ckEJuZLMZ+N500c34qWH iKxNnksZN/+iXgsxXJXHnDwtd20HTGxJW/VWBpak5HsyiymofefM7qNMNDdvdZY1A7Uy+0 UcZknqqJ1O9IaiUL1SGltbKZ2BMmw3CacYrNC1LDzYgntK6COp6q5AAVSBJYY+WsONCxM0 5tmg972NZYBMnKp8NMlkSfXjF7kh8fxfdpMGnUPzV55ZQ1KDrw4lYEmIaAQwjg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1685186720; a=rsa-sha256; cv=none; b=ZBnWUz4f0UQJgRW0tabSNIUvtma66Q7uQZuSHgLsDFY4qI07YmqU62rg84k4MVLhMJ2/yI kAUDIq6eobcc8sMx8s5O3sSnke3x82GGktUsj5ijyzPPXQ6iTuIpYhS4MadE0z7gVyr5zk eiJ9Z95E0NXKB281ZKAHzztAUfJkJrFdyP1EVZs75hJ6f+LLLkPUz9Bp+fWMmCKLWHMkN/ cxBk4ZqrTeUbBsAklHkNbUhkfLEWJ9obnw2uidLr1XvrSJIVrOr6gY4xhroaB5EZ55o9gZ Rrv90AJdmqEL8G0AKulh6A6g19Zm91Q2ir232UUToEckhFl0Vcm9G1gJEpqJsQ== Received: from mail-ej1-f44.google.com (mail-ej1-f44.google.com [209.85.218.44]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) (Authenticated sender: sunpoet) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QSzww4XRVz1QHq for ; Sat, 27 May 2023 11:25:20 +0000 (UTC) (envelope-from sunpoet@freebsd.org) Received: by mail-ej1-f44.google.com with SMTP id a640c23a62f3a-96f0678de80so291282266b.3 for ; Sat, 27 May 2023 04:25:20 -0700 (PDT) X-Gm-Message-State: AC+VfDwfb1fHAboc52kOd9NdjI7Fa2V1yQO9F0SaIEQoZLFFaPTKCrEr Vb020/mLxlfF8yY8M+nKNX1vPjzpWVoNKo+VIhBWGA== X-Google-Smtp-Source: ACHHUZ60EzI+6S5BEtUEHdvrJfTOpIZCvacEjrMaJoCxHSHOr50LGzZNM3LU1dv0IdwwWNv8Q6sm+eR4cZNAsDZuBTk= X-Received: by 2002:a17:907:781:b0:96a:43b9:95b1 with SMTP id xd1-20020a170907078100b0096a43b995b1mr4413365ejb.59.1685186719290; Sat, 27 May 2023 04:25:19 -0700 (PDT) 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 References: <3e5e10a3-75e7-795e-edbf-378bcb4999a4@FreeBSD.org> <061bc038-bf20-ad47-f571-eb153ccce092@FreeBSD.org> In-Reply-To: <061bc038-bf20-ad47-f571-eb153ccce092@FreeBSD.org> From: Po-Chuan Hsieh Date: Sat, 27 May 2023 19:24:42 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: graphics/podofo: 0.10.x requirement To: Guido Falsi Cc: Kurt Jaeger , "ports@FreeBSD.org Ports" , Po-Chuan Hsieh Content-Type: multipart/alternative; boundary="000000000000c8cf2a05fcab1b33" X-ThisMailContainsUnwantedMimeParts: N --000000000000c8cf2a05fcab1b33 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, On Fri, May 26, 2023 at 11:18=E2=80=AFPM Guido Falsi = wrote: > 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 b= e > >> installed in parallel with graphics/podofo (by changing the name of > >> every file installed that conflicts), so that ports moving to the newe= r > >> 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. > I believe that netbox is not this case, at least slightly different. It's not old/new versions but LTS/non-LTS versions. The ports with py-django- prefix follow the LTS version. And we add djXX- prefix to non-LTS versions, e.g. py-dj{40,41}-. When the new LTS django comes out, kai@ will update py-django-* ports. Regarding gitlab, I guess you mean rubygem ports, I keep rubygem ports mostly the way as plan 2. In most cases, the port without suffix is the latest version and ports with suffix are older versions. > > >> 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/podofo= 09 > >> (or whatever) port, updating all dependencies to use the older port fo= r > now. > > > > Also fine. > > I'd like to choose plan 2. > > > 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, do you have a patch for podofo and calibre already? Since podofo has only 5 dependent ports, it should be possible to test them all with podofo (0.10.0) and move incompatible ones to podofo09. > > -- > Guido Falsi > > --000000000000c8cf2a05fcab1b33 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,

On Fri, May 26, 2023 at 11:18=E2=80=AFPM Guido Falsi <madpilot@freebsd.org> wrote:
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 inco= mpatible
>> 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 maintain= er,
>> is, how should we address this?
>>
>> Also, is this already being addressed, maybe?
>>
>> We can't simply update graphics/podofo, obviously (all depende= nt ports
>> would brake).
>>
>> Plan 1 - My first idea is creating a graphics/podofo10 port that c= an be
>> installed in parallel with graphics/podofo (by changing the name o= f
>> 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 someti= mes.
>
> netbox and gitlab often have such cases.

I believe that netbox is not this case, at least slightly different.=
It's=C2=A0not old/new versions but LTS/non-LTS versions.
The ports with py-django- prefix follow=C2=A0the LTS version.
<= div>And we add djXX- prefix to non-LTS versions, e.g. py-dj{40,41}-.
<= div>When the new LTS django comes out, kai@ will update py-django-* ports.<= br>
=C2=A0
Regarding gitlab, I guess you mean rubyg= em ports, I keep rubygem ports mostly the way as plan 2.
In most = cases, the port without=C2=A0suffix is the latest version and ports with su= ffix are older versions.

>
>> plan 2 - Another option is doing the same as above, but my updatin= g
>> podofo to the latest version and moving old 0.9.x to a graphics/po= dofo09
>> (or whatever) port, updating all dependencies to use the older por= t for now.
>
> Also fine.
>

I'd like to choose plan 2.
=C2=A0


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, do = you have a patch for podofo and=C2=A0calibre already?
Since = podofo has only 5 dependent ports, it should be possible to test them all w= ith=C2=A0podofo (0.10.0) and move incompatible ones to podofo09.
= =C2=A0

--
Guido Falsi <madpilot@FreeBSD.org>

--000000000000c8cf2a05fcab1b33--