From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: new category for container related packages, instead of app-emulation
Date: Sat, 07 Aug 2021 08:24:47 +0200 [thread overview]
Message-ID: <8bf61d3fe6ce6ece10b6e77fd12f36b3ee921d20.camel@gentoo.org> (raw)
In-Reply-To: <CAAr7Pr-PoAjLcC8-HmJ-PMUkuTr5u1=PYTVZT5KPkLDMDxLTyQ@mail.gmail.com>
On Thu, 2021-08-05 at 17:57 -0700, Alec Warner wrote:
> On Thu, Aug 5, 2021 at 2:44 PM Georgy Yakovlev <gyakovlev@gentoo.org> wrote:
> >
> > Hi,
> >
> > We've been collecting more and more container related packages in
> > app-emulation/*
> >
> > What do you think about finally moving those packages to separate category?
>
> As always my opinion is that:
>
> (a) Categories were a design mistake.
> (b) The mistake is hard to fix.
> (c) It's basically low-value to try to 'correctly' categorize packages
> because of A.
> (d) Recategorizing means a bunch of stuff has to be updated.
>
Categories themselves were not a design mistake. The design mistake is
using categories to permit conflicting package names.
Categories are convenient. Sure, they're not perfect but they serve
their purpose to some degree and there's little harm in having them.
If you want to organize packages better, nobody's stopping you. Until
you've got a better and widespread replacement, I don't see why people
shouldn't be using categories as they see fit.
The other part is something we could aim for fixing but so far most
developers seems to disagree with me, so there's no point in pursuing
that.
--
Best regards,
Michał Górny
next prev parent reply other threads:[~2021-08-07 6:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 21:44 [gentoo-dev] RFC: new category for container related packages, instead of app-emulation Georgy Yakovlev
2021-08-06 0:01 ` Aaron Bauman
2021-08-06 0:57 ` Alec Warner
2021-08-06 3:46 ` Thomas Mueller
2021-08-06 18:58 ` A Schenck
2021-08-07 17:19 ` A Schenck
2021-08-06 21:12 ` William Hubbs
2021-08-07 0:48 ` Alec Warner
2021-08-06 21:17 ` Toralf Förster
2021-08-06 22:27 ` Louis Sautier
2021-08-07 4:56 ` Sam James
2021-08-07 5:17 ` Ionen Wolkens
2021-08-08 11:37 ` Eray Aslan
2021-08-07 1:49 ` Joshua Kinard
2021-08-07 6:24 ` Michał Górny [this message]
2021-08-07 21:06 ` Andreas K. Huettel
2021-08-06 7:42 ` Florian Schmaus
2021-08-06 22:23 ` 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=8bf61d3fe6ce6ece10b6e77fd12f36b3ee921d20.camel@gentoo.org \
--to=mgorny@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