From: Tim Harder <radhermit@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] pkgdev: an alternative to `repoman commit`
Date: Sat, 27 Feb 2021 07:50:11 -0700 [thread overview]
Message-ID: <YDpcI5pAVxB5yFcU@fir> (raw)
Hi all,
Finally responding to all the requests, I've hacked up an initial
alternative to repoman's commit functionality in the form of pkgdev [1]
that uses pkgcheck's API behind the scenes. The project is meant to grow
into a collection of tools for Gentoo development and maintenance, but
initially supports `pkgdev commit` and `pkgdev push` that should work
for a basic git workflow on ebuild repos.
In essence, `pkgdev commit` wraps `git add` and `git commit`
functionality along with supporting GLEP 66 style message prefixes for
any committed files across an ebuild repo. Package manifests are also
regenerated and added automatically for any targeted pkg commits.
QA scanning is done on `pkgdev push` (not per `pkgdev commit` call) so
knowing/learning how to interactively `git rebase` is currently
essential to the workflow. Probably the main thing lacking is good docs
for the workflow that pkgdev envisions as it differs slightly from the
one used with repoman.
Feel free to respond with questions, ideas, or flames. If you want to
give it a shot, I believe a live ebuild for it has already been added to
the tree at dev-util/pkgdev. Also, please open issues on the upstream
project if you run into bugs or have feature requests.
Thanks,
Tim
[1]: https://github.com/pkgcore/pkgdev
next reply other threads:[~2021-02-27 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 14:50 Tim Harder [this message]
2021-02-27 15:22 ` [gentoo-dev] pkgdev: an alternative to `repoman commit` Sam James
2021-02-28 2:04 ` Louis Sautier
2021-02-28 17:51 ` Tim Harder
2021-03-05 22:39 ` Tim Harder
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=YDpcI5pAVxB5yFcU@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