From nobody Fri Jan 03 12:02:41 2025 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 4YPhzP28yyz5jtvJ for ; Fri, 03 Jan 2025 12:02:57 +0000 (UTC) (envelope-from ps.ports@smyrak.com) Received: from ipv6.s149.cyber-folks.pl (ipv6.s149.cyber-folks.pl [IPv6:2a02:1778::113:254]) (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 4YPhzP001yz47tc for ; Fri, 3 Jan 2025 12:02:56 +0000 (UTC) (envelope-from ps.ports@smyrak.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smyrak.com; s=x; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References: In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=c5P3DucmISG7rG3ZJK8GsSwFjZ7a47eJ7bEUrKcC+qk=; b=Cmrg+p1L9h+ESnTt89LICjwoRo u2XfTfAztnhmR/FuRTGUanydfuToobyApj/zRtY89lKOXRTeR4w9yGyTh4YtR0n9mE0ReId2ybTOx o1CtTuC1m26Zla/IzQRPP4IHKczyAv6vvyEZbmZwhy1rbYvVgv/Le91NuskzLuxm5iHmR3DmYxEtR IcDvELRSzyCX5bUgZ5dHCW2EWBjxrk3EyBvIwdy5ZB1OKFvpzOk53carSuohycDwP8kJJqIDvmNWW 8UA9pVSbYxke6Llw0i0niZ7WqC6+xNjM8zH45fcnqmph94ArG3VYQRdxyN8R3F0ih5Ih3E33hvqh3 qPxPJy7Q==; Received: from 93-181-165-201.internetia.net.pl ([93.181.165.201] helo=daleth.home) by s149.cyber-folks.pl with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.98) (envelope-from ) id 1tTgOF-00000007RIY-2Y8d; Fri, 03 Jan 2025 13:02:55 +0100 Date: Fri, 3 Jan 2025 13:02:41 +0100 From: Piotr Smyrak To: FreeBSD Ports ML Cc: Xavier Humbert Subject: Re: Why does it take so long to build some Python ports Message-ID: <20250103130241.00fa8099@daleth.home> In-Reply-To: <6a3ab2e1-9d33-4a3e-9fd5-c1d86a91ec46@groumpf.org> References: <6a3ab2e1-9d33-4a3e-9fd5-c1d86a91ec46@groumpf.org> List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-ports@freebsd.org Sender: owner-freebsd-ports@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Authenticated-Id: piero@smyrak.com X-Rspamd-Queue-Id: 4YPhzP001yz47tc X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:41079, ipnet:2a02:1778::/48, country:PL] On Fri, 3 Jan 2025 08:41:08 +0100 Xavier Humbert wrote: > Some, but not all python ports spend a long time in building eggs >=20 > Ex : >=20 > running egg_info > writing src/charset_normalizer.egg-info/PKG-INFO > writing dependency_links to=20 > src/charset_normalizer.egg-info/dependency_links.txt > writing entry points to > src/charset_normalizer.egg-info/entry_points.txt writing requirements > to src/charset_normalizer.egg-info/requires.txt writing top-level > names to src/charset_normalizer.egg-info/top_level.txt >=20 > *pstree -w *shows : >=20 > | |=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 \-+- 64353 root /usr/local/bin/python3.11 -m build=20 > --no-isolation --wheel > | |=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 \-+- 64468 root /usr/local/bin/python3.11=20 > /usr/local/lib/python3.11/site-packages/pyproject_hooks/_in_process/_in_p= rocess.py=20 > build_wheel /tmp/tmptnbyl41r > | |=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 \--- 64471 root git archive --prefix > /usr/ports/ HEAD >=20 > What is the purpose of *git archive* ? There is no invocation of "git archive" in /usr/ports/Mk/Uses/py* Python port mechanism, in fact neither in the whole subtree of /usr/ports/Mk. Which means this is not ports that make use of it, but rather upstream tooling. I suspect what you are observing is actually a code if the py-setuptools-scm package: Name : py311-setuptools-scm Version : 8.0.4 Origin : devel/py-setuptools-scm WWW : https://github.com/pypa/setuptools_scm Comment : Setuptools plugin to manage your versions by scm tags Description : Handles managing your python package versions in scm metadata instead of declaring them as the version argument or in a scm managed file. HTH, --=20 Piotr Smyrak