From nobody Sat Oct 07 12:30:16 2023 X-Original-To: freebsd-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 4S2l4j0qfzz4wCpy for ; Sat, 7 Oct 2023 12:30:29 +0000 (UTC) (envelope-from eduardo@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 4S2l4j0FM7z4LFG; Sat, 7 Oct 2023 12:30:29 +0000 (UTC) (envelope-from eduardo@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1696681829; 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=3T8drs6SdtpPCPHDrH+mTBBleuZcYlI2R8TKTKVqqpw=; b=Qkpv4MIuWWZ6tHcVbYU5NJPSmhTV2ihJ4J0EFbSgQpU35lU2J7BQIEgcLvRKz6q4t3taxQ tKKmT+d8tJPIQ38e+Z2qm96w4Sj8U2vIQOUOz5ceglO8L6gQ1Vzs4xzsfB8iKnAcWzOwWv tk9wvDjD5upNJfoU2WWlxo0tyg/9ybLN4nVHrp3AwgHZY89KqdN7UO4GnjeA/3oEeNDwJJ z3POdojxrYubmFAc8y4KorzMlTUm3/LlGmpx0dy79N2PREO6rEvp7uS6XO0Q90Yy84fd7j 0egHpVxTCjwXyOBshgvgMkaexOL2mZCXth+CTscXduBHk2ZyG5o08xfWGxVMSQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1696681829; a=rsa-sha256; cv=none; b=fr4UL5ofh5zY2EOxbwpATYhXd1TnhaL5JJ/B8GqhwcvD+UF4EDGh4eXuvxckJkHZw8xQg4 QJsLnY/d0LNywF7kcScCQEvLima9BnVp2NOHaGtx54eVblWgqi/kcc5y76c10ZsZWBa+Bh tR1tAUOHqIULPHHLmIkmjyNLqoikfN9zhsHytzg2Zyl2Xn8O9moYmBodPdS463w4m9UdIA UEtOAJRUVK7lnG6RM+PrSCSNd6QTNmApkDgdRXRixgcOwiBBIkcYh6nqiX+G7cFw0LndTn MqMvvILiWF+COu5yiOZBWn84u+Ejirb2uq9QwvO0OSvYz9bCpGPyE6XhMgTI3Q== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1696681829; 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=3T8drs6SdtpPCPHDrH+mTBBleuZcYlI2R8TKTKVqqpw=; b=tPJBHfg0II8pbcSOh1UqOrXyoa67Ba9GswzK2fVNXR6knGt4wOEL2wYUXNrQUgu6RW3M4F oL1OYo/NVshuenkPIR7XNAuPF3GPexxD6d6SjWUrQ95HaGxqm4m8qCH1n+4eZSGLM9++9o GVLk9Z744zmUKn1Ibh6QG+t7nkfFcCjfPDlfk7gKJ6pFdOsIAvJcxwxAdDEjFF3W8DL12i KoZPAeZl+YAOnZ9jYC4yZgk0g708f6LagAEiH4fOnKNnjlP/MvDqTgoGY9ugdzXDPQm9s6 6ZxZUuMmk+zMSmf6chnH489FJX6FMWs2PRTTMvtkqrBNtlE2Fhw6Hoqr+9uExA== Received: from mail-qt1-f174.google.com (mail-qt1-f174.google.com [209.85.160.174]) (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: eduardo) by smtp.freebsd.org (Postfix) with ESMTPSA id 4S2l4h6J1Dzm9p; Sat, 7 Oct 2023 12:30:28 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: by mail-qt1-f174.google.com with SMTP id d75a77b69052e-4190890d201so17159191cf.2; Sat, 07 Oct 2023 05:30:28 -0700 (PDT) X-Gm-Message-State: AOJu0Yz451ITnMNZ156WMxpg6OgNLR4x1zkKrcb5bHL0Ytm4KtmaER0r WrKkmw1gp6PAaH9ilOPTtuyYk0pxxzudR4bjkGA= X-Google-Smtp-Source: AGHT+IFxQOpn3dLWcy5hWgxXeoXfLLtrp+lO1VhTStoW9FKusZIX46LScWK0GHxpdLZdL/hUGhciKekMxKGXLq9Y4a0= X-Received: by 2002:a05:622a:1009:b0:415:138e:d858 with SMTP id d9-20020a05622a100900b00415138ed858mr10297796qte.60.1696681828189; Sat, 07 Oct 2023 05:30:28 -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: <1212FFB4-B9D2-4303-8817-82542F94DE53@freebsd.org> <682E3500-EE71-4DEB-8B82-0BF4158DD0FA@freebsd.org> In-Reply-To: <682E3500-EE71-4DEB-8B82-0BF4158DD0FA@freebsd.org> From: Nuno Teixeira Date: Sat, 7 Oct 2023 13:30:16 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Port update and consumers bump To: Moin Rahman Cc: Kurt Jaeger , FreeBSD Mailing List Content-Type: multipart/alternative; boundary="000000000000aa8bf006071f8550" --000000000000aa8bf006071f8550 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks Moin! Now I have understand it. I will use: git grep -e 'USE_WX' --and \( -e 3.0+ -e 3.2 \) Looks for a line that has USE_WX and either 3.0+ or 3.2. (3.2+ will be included too) Cheers Moin Rahman escreveu no dia s=C3=A1bado, 7/10/2023 =C3= =A0(s) 13:03: > > > > On Oct 7, 2023, at 2:00 PM, Nuno Teixeira wrote: > > > > > > This 3.2 search might be counterproductive as we have an option "3.0+" > which also indicates 3.2 as a valid value. > > > > ports with 3.0+ will use 3.0 for building without changes . For this > particular update involving 3.2 shouldn't we focus on consumers using 3.2 > only? > > The answer is both yes and no. :) > > There are some corner cases like let's say there is port A which was buil= t > using 3.2 and there is now port B which has 3.0+ and is now being built. > There is a high chance that it will use the already available 3.2 rather > than building 3.0. That's why it's better to be safe than sorry and also > bump those ports. > > Kind regards, > Moin(bofh@ with all hats off) > --=20 Nuno Teixeira FreeBSD Committer (ports) --000000000000aa8bf006071f8550 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks Moin!

Now I have unde= rstand it.

I will use:

gi= t grep -e 'USE_WX' --and \( -e 3.0+ -e 3.2 \)
Looks for a= line that has USE_WX and either 3.0+ or 3.2. (3.2+ will be included too)

Cheers

Moin Rahman <bofh@freebsd.org> escreveu no dia s=C3=A1bado, 7/10= /2023 =C3=A0(s) 13:03:


> On Oct 7, 2023, at 2:00 PM, Nuno Teixeira <eduardo@freebsd.org> wrote:
>
>
> This 3.2 search might be counterproductive as we have an option "= 3.0+" which also indicates 3.2 as a valid value.
>
> ports with 3.0+ will use 3.0 for building without changes . For this p= articular update involving 3.2 shouldn't we focus on consumers using 3.= 2 only?

The answer is both yes and no. :)

There are some corner cases like let's say there is port A which was bu= ilt using 3.2 and there is now port B which has 3.0+ and is now being built= . There is a high chance that it will use the already available 3.2 rather = than building 3.0. That's why it's better to be safe than sorry and= also bump those ports.

Kind regards,
Moin(bofh@ with all hats off)


--
Nuno Teixeira
FreeBSD Committ= er (ports)
--000000000000aa8bf006071f8550--