public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tim Harder <radhermit@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] pkgcraft: yet another package manager spec implementation
Date: Thu, 22 Jun 2023 15:24:27 -0600	[thread overview]
Message-ID: <ZJS8C3DKnWnE7Muu@fir> (raw)

Hello all,

As some already know, for about two years I've been working on
pkgcraft[1] which is yet another implementation of the package manager
specification (PMS). Having recently achieved the milestone of
functionally supporting metadata generation for the tree[2], I thought a
wider audience might be interested to learn about the project.

In short, pkgcraft is a highly experimental tooling ecosystem for
Gentoo. From a design standpoint, it's mainly implemented in rust,
bundles its own extended version of bash allowing all PMS functionality
to be implemented as builtins, and provides a C library that language
bindings can build from -- currently python, ruby, go, and perl bindings
exist at varying states of API coverage.

The design enables some unique approaches and tools such as helping devs
target and improve wildly inefficient bash code. Recently it was
leveraged for eclass rework that cut full tree metadata generation time
in half for pkgcraft with the gentoo repo. 

For those interested in more detailed information about the project and
its development, see the FAQ[3], dev blog[4], or join the #pkgcraft
channel on libera.

Thanks,
Tim

[1]: https://github.com/pkgcraft
[2]: https://pkgcraft.github.io/posts/metadata-cache-generation/
[3]: https://pkgcraft.github.io/about/
[4]: https://pkgcraft.github.io/


                 reply	other threads:[~2023-06-22 21:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ZJS8C3DKnWnE7Muu@fir \
    --to=radhermit@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