public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Arthur Zamarin <arthurzam@gentoo.org>
Subject: Re: [gentoo-dev] Arch Status and Future Plans
Date: Wed, 26 Jun 2024 22:18:40 +0200	[thread overview]
Message-ID: <23555036.6Emhk5qWAg@pinacolada> (raw)
In-Reply-To: <75654daa-c5fc-45c8-a104-fae43b9ca490@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1623 bytes --]

> ======== alpha ========
> 
> Exp arch, with nearly (or maybe already) full correct dep-tree. matoro
> did a lot of great work here, so I think we should promote it to dev
> arch, so dep-tree remains unbroken. We dekeyworded a lot of stuff,
> cleaned it up, so a nice "completion bonus".
> 
> ======== m68 ========
> 
> Exp arch, works ? maybe? I've no idea. Let's not touch :)
> 
> ======== mips ========
> 
> Exp arch, with mostly good dep-tree. Does mips team want to make it dev
> arch?

What you call "exp arches" (i.e. architectures with no "stable profiles" at
all) are a pain in the behind. Nobody checks if dependencies are correct, 
and the dependency tree becomes randomly broken.

This should ideally only be a temporary status, 
* either on the way to a consistent deptree (~arch)
* or on the way out the door.

My 2ct:

alpha: well, if it is in a decent state, and if Matoro promises to keep up
with keywording requests (important!), let's upgrade it.

m68k: dito as soon as Chewi thinks it's ready

mips: well... personally I'd love to have it back to a consistent deptree, 
but right now it has still waaay too many packages keyworded for that.
also, this is a horrible beast, with 32bit, mixed, and 64bit ABI and both
big and little endian. we have no hardware at all, and even if we had it
would be slow... 
that said, I dont see us dropping support for mips either. in particular
since we're one of the last distros to deal with it...




-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

  parent reply	other threads:[~2024-06-26 20:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25 17:33 [gentoo-dev] Arch Status and Future Plans Arthur Zamarin
2024-06-25 21:40 ` matoro
2024-06-25 22:55 ` James Le Cuirot
2024-06-26  0:06 ` Notion of stable depgraph vs stable keywords (Re: [gentoo-dev] Arch Status and Future Plans) Sam James
2024-06-28  4:17   ` [gentoo-dev] Re: Notion of stable depgraph vs stable keywords (Re: " Duncan
2024-06-28  5:16     ` Sam James
2024-06-26  0:14 ` Misc arch plans (Re: [gentoo-dev] " Sam James
2024-06-26 20:29   ` ia64, was: " Andreas K. Huettel
2024-06-26 20:45     ` matoro
2024-06-26  0:17 ` On the value (or not?) of stable keywords " Sam James
2024-06-26  0:19 ` time64 & LFS for 32-bit arches " Sam James
2024-06-26  0:20 ` x86 FP issues " Sam James
2024-06-28  5:20   ` Michał Górny
2024-06-26  7:38 ` [gentoo-dev] Re: Arch Status and Future Plans Florian Schmaus
2024-06-26  8:29   ` Christian Bricart
2024-06-26 20:44   ` Immolo
2024-06-26 19:47 ` nomenclature, was: Re: [gentoo-dev] " Andreas K. Huettel
2024-06-26 20:18 ` Andreas K. Huettel [this message]
2024-06-26 20:24 ` riscv, " Andreas K. Huettel
2024-06-26 21:08 ` 32bit vs 64bit, " Andreas K. Huettel
2024-06-28 16:12 ` splitting keywords, " Andreas K. Huettel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=23555036.6Emhk5qWAg@pinacolada \
    --to=dilfridge@gentoo.org \
    --cc=arthurzam@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox