From nobody Fri Oct 14 18:33:52 2022 X-Original-To: dev-commits-ports-main@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 4Mpw5M40SPz4g246; Fri, 14 Oct 2022 18:33:59 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (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 "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Mpw5M3PYVz3SBm; Fri, 14 Oct 2022 18:33:59 +0000 (UTC) (envelope-from jbeich@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1665772439; 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=IQg+eBjj40PI5b5sIZSBCN1D1C/JE8myavxxofROJls=; b=GIAiG7ra1gBc6+EaKn4RHtXcEOALc4gbAPGwQHALwteRiD5xIxmAaAmg9ueNouzdMQs3AC 0NGLpI+6UsVB6z38WtiKj4urtNPeJX7/dqNIy81J0Zu94bk94laBYyd1R1bRPk+emP5bpP imFLRjfzCUS6/CJQoBlFK+SP0v8zOB/G/bfECLYUSck4EE8zNJu6+0WCueKTGMOtaZFNVl 6/o7smFSw5Dp5vh/XMvNzDj8w7MA9ZZsB5UlY+xqQC0Ry/t226p+84MJ7/7WXSfOngvLw8 jqwd5JFZxVZsZnSi7MEW1KxWoueZ2pMK2tu0eFYDh07ozO/3v7P8FGh78/mgSQ== Received: by freefall.freebsd.org (Postfix, from userid 1354) id 5626F7316; Fri, 14 Oct 2022 18:33:59 +0000 (UTC) From: Jan Beich To: Adam Weinberger Cc: ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: 9d241a90370c - main - Mk: Add USES=luajit In-Reply-To: (Adam Weinberger's message of "Fri, 14 Oct 2022 11:29:03 -0600") References: <202210141707.29EH7i08013647@gitrepo.freebsd.org> Date: Fri, 14 Oct 2022 20:33:52 +0200 Message-ID: List-Id: Commits to the main branch of the FreeBSD ports repository List-Archive: https://lists.freebsd.org/archives/dev-commits-ports-main List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-dev-commits-ports-main@freebsd.org X-BeenThere: dev-commits-ports-main@freebsd.org MIME-Version: 1.0 Content-Type: text/plain ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1665772439; 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=IQg+eBjj40PI5b5sIZSBCN1D1C/JE8myavxxofROJls=; b=CPN8Vu9/PznyUJZ/P1rgjdnSaAUOirBpXOsR60M9FGH/gnmPG0bBMj0ue8Ohja/yDNKk7U yZMYEOleBuX42FpUWe7rF4jszFtB0T+2C496998TzLzpVsJq2Cd0PGz+YL3knOCQSRNGIE 2v81ivh4mMXPJEtTasCLw6GbXGVOH+OaT6fpJWZbYqPHYHP7R+dT1LQmDyHU4q73e2WIlL 092c1MTbsyo17Sbvdjb+eXt7svk9juUeA82lTF+b2iBmHkfJ0j7yC3Qhrxn0PmcZornKiY yby7Ljbo58hghVtBw2yL4gg5sDXyTEiHjeaV0v7Vu14kresl0lYFzpKCOawIgw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1665772439; a=rsa-sha256; cv=none; b=SFhz9aqcuDUOFTAso1udizNkGb85Su9WHDLPUpT10iuHS5oHumb8M976UcNOYqlcGOnVsG aALKYGk4/wYyznCLSmsSJx+dfGmF/v6nVqldmyaUH/ovO/yOXXMEatZ8qMYFo+H9tSeiku tRo5UQXGyU5FmplHa/fzLOrkjBvQ1tG1BhjG6U019WbnptmVHVVaw3fIW2sOy1qJCzWT9K 0MtUv88KdU0HC6vArDa+xua4oa+shYljqWuloJFV+xgnVU1rTN4ONjTomBLNr2GwiqCImu PDUZ5oVlcAIgWTm8P5WzuE+8kkRKmVwXZNy5CjxDT7kzDN6DG86FM39FEXD2FQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N Adam Weinberger writes: > On Fri, Oct 14, 2022 at 11:25 AM Jan Beich wrote: > >> Adam Weinberger writes: >> >> > For the vast majority of situations, USES=luajit will be sufficient. >> > Ports that use openresty's API additions can specify >> > USES=luajit:openresty. >> >> Are consumers to be switched "en masse" or "one by one"? >> > > Hi Jan, > > I'm going to switch a couple ports (neovim and luv) right now, but my > thinking is that perhaps the best approach is two exp-runs. The first run > can switch everything depending on lang/luajit to USES=luajit. For the > second run, I'll need to look at everything that depends on > luajit-openresty to find out whether it uses it because it uses the > openresty API or because what they actually wanted was "anything other than > the old version in lang/luajit." > > Does that sound sensible? Probably: - exp-runs can be reduced via local testing as USES=luajit only has ~50 candidates - luajit -> luajit-devel is safe due to same upstream and tested by other distros - luajit-openresty -> luajit-devel build test may show false negatives[1] but ARCH-specific cases are likely safe [1] www/openresty and {devel,www}/lua-resty-* build fine with lang/luajit-devel. However, not every instance maybe as obvious whether to ask maintainer.