From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: New category for AI related packages
Date: Tue, 11 Mar 2025 19:07:11 +0100 [thread overview]
Message-ID: <uy0xba1bk@gentoo.org> (raw)
In-Reply-To: <Z9BxDgbqNiHrDmOz@sysrq.in> (Anna Vyalkova's message of "Tue, 11 Mar 2025 22:21:18 +0500")
[-- Attachment #1: Type: text/plain, Size: 643 bytes --]
>>>>> On Tue, 11 Mar 2025, Anna (cybertailor) Vyalkova wrote:
>> Let's call it "sci-machine-learning/".
> Looks good, but would be better without the second hyphen:
> "sci-machinelearning". Kind of similar to "app-mobilephone".
> There is indeed no limit on the category name length or structure in
> the PMS. The way they are named in Gentoo is just a tradition.
There are good reasons to keep the total path length short. For example,
test suites may break if the directory path under PORTAGE_TMPDIR is too
long (and I learned this the hard way).
The category name is a good place to start because it affects multiple
packages.
Ulrich
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]
prev parent reply other threads:[~2025-03-11 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 17:21 [gentoo-dev] Re: New category for AI related packages Anna (cybertailor) Vyalkova
2025-03-11 18:07 ` Ulrich Müller [this message]
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=uy0xba1bk@gentoo.org \
--to=ulm@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