From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 05BE715802E for ; Wed, 26 Jun 2024 19:47:18 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B12C2E2B02; Wed, 26 Jun 2024 19:47:12 +0000 (UTC) Received: from smtp.gentoo.org (mail.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (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) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 5826DE2AD7 for ; Wed, 26 Jun 2024 19:47:12 +0000 (UTC) From: "Andreas K. Huettel" To: gentoo-dev@lists.gentoo.org Cc: Arthur Zamarin Subject: nomenclature, was: Re: [gentoo-dev] Arch Status and Future Plans Date: Wed, 26 Jun 2024 21:47:04 +0200 Message-ID: <3227107.5fSG56mABF@pinacolada> Organization: Gentoo Linux In-Reply-To: <75654daa-c5fc-45c8-a104-fae43b9ca490@gentoo.org> References: <75654daa-c5fc-45c8-a104-fae43b9ca490@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart5950747.MhkbZ0Pkbq"; micalg="pgp-sha512"; protocol="application/pgp-signature" X-Archives-Salt: 2a7e5f8b-e10f-4cc4-b235-327b46d964b3 X-Archives-Hash: 600134d049093dd7de80e95b252595c6 --nextPart5950747.MhkbZ0Pkbq Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; protected-headers="v1" From: "Andreas K. Huettel" To: gentoo-dev@lists.gentoo.org Cc: Arthur Zamarin Date: Wed, 26 Jun 2024 21:47:04 +0200 Message-ID: <3227107.5fSG56mABF@pinacolada> Organization: Gentoo Linux In-Reply-To: <75654daa-c5fc-45c8-a104-fae43b9ca490@gentoo.org> References: <75654daa-c5fc-45c8-a104-fae43b9ca490@gentoo.org> MIME-Version: 1.0 > As you all know, Gentoo supports many various arches, in various degrees > (stable, dev, exp). Let me explain those 3 statuses fast: >=20 > * stable arch - meaning we have stable profile for this arch, and stable > keywords across base-system + varying degree of seriousness. We stable > stuff after ~30 days in tree, and are mostly happy. For example the well > known and common amd64 arch. >=20 > * dev arch - meaning we have complete dep-tree (no broken dep-trees), > but no stable profile. If you break here a package (for example > introduce new dep, previously unkeyworded) you are expected to dekeyword > and ask for rekeywording. For example the nearly unknown arch s390. >=20 > * exp arch - meaning we support what we support, with possible broken > dep-tree. This is the "scary" state of arch, since it can break at any > moment. For example the noisy (because of the physical fans) arch alpha. This classification is good enough for practical purposes (and for the discussion of the status of architectures) but technically not correct. I'll try to clarify below, but mostly to clean up confusion about wording. You have to keep apart two things, A) architecture status, and B) profile status, which are formally independent of each other. A) architecture status, defined in profiles/arches.desc A.1) stable amd64, arm, arm64, hppa, ppc, ppc64, sparc, x86 Architectures that have a stable keyword and where packages undergo stabili= zation. A.2) transitional (currently none) Architectures that have a stable keyword and where packages undergo stabili= zation,=20 but the dependency tree is only consistent for ~arch. This is useful for upgrading architectures to stable. A.3) testing all other Architectures that only have testing, ~arch keywords B) profile status, defined in profiles/profiles.desc B.1) stable The dependency tree is checked and enforced by the CI and by pkgcheck by de= fault. Unsatisfied dependencies etc generate errors and "break the tree". B.2) dev The dependency tree is checked by the CI and by pkgcheck (by default). Unsatisfied dependencies etc generate warnings. B.3) exp No checking (by default) Many combinations of these two properties exist. For example,=20 amd64: is A.1 and has many B.1 profiles (but also some B.2 and B.3) loong: is A.3 and has B.1, B.2, B.3 profiles m68k: is A.3 and has only B.3 profiles =2D-=20 Andreas K. H=FCttel dilfridge@gentoo.org Gentoo Linux developer (council, toolchain, base-system, perl, libreoffice) --nextPart5950747.MhkbZ0Pkbq Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQKTBAABCgB9FiEE/Rnm0xsZLuTcY+rT3CsWIV7VQSoFAmZ8cDhfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEZE MTlFNkQzMUIxOTJFRTREQzYzRUFEM0RDMkIxNjIxNUVENTQxMkEACgkQ3CsWIV7V QSrPHQ//UvVuWgLm5zW5B7/ZmqLFWfQv2u1EEeA3aJhFYfqxyxG0w34buhqDDRBg UaP0EWUSFRzgwTvHpqaucw7w3tMrcg7ajkQGu3ZNeYcGvUyA/tsQChrekn9BYG2d y1XCfUmROsK/xFmI2wQURD8M46F0lu39BQL0sQNH8kg3XLx367rasR4socbav5Wk mfnScSMBommMmKPOTN+k/2DVyYHsyMdWl6FpFCPxEFBs5Ghk4mosps6NtzF5pjgi oPjR0S3mKD3GPnv2AumzXJfuatcF4FfTwextnxyk7Tama+CW97mtN1ZhQKimBrgk Wjtr4f3lY8gcQ+UH/3ndIUB73FCrxW9Jd2a6kE97P/YwcXPU09SekDArvZQogUJ8 yONlkkuFgNbJYKejqNpWDlWCeyA6tf0MLEGUNl2rDRWlHaph2qn9p3iCscKXkRFT q4Ut8IgJN+Zf0uVq1swW4ChcusHNxUpE/eHALin1BAXlJ9qBWc9I9duRLqovJ5sN vSgN8cBMola1OBbXgyX4b+VP5CFDKObUEFjfhG1vYQaWJ6IKFco2pRPVqP2pwPh5 Q2JxvatlldcHshWLxEZP5UYuDvILABTrdIYfLNsUbrKPsMK94VA8Wwz+Mwji5GBZ ngBCvJNS4Ga1sctx3zmpow1PHEsFHsgVy7WXtm6quw2HoPPTzvM= =oYoO -----END PGP SIGNATURE----- --nextPart5950747.MhkbZ0Pkbq--