[gentoo-dev] pkgdev: an alternative to `repoman commit`

[Tim Harder]

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

[Sam James]

> On 27 Feb 2021, at 14:50, Tim Harder <radh...@gentoo.org> wrote:
>
> 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.

Thank you! Already using it.

> [snip]

>
> 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.

Yes, please let me know if there’s any issues with the ebuild too.

I’ll add a tagged release once it’s made, obviously.

[Louis Sautier]

Hi Tim,
That's really nice, thanks!
I just tested it and it seems really nice, I just need to adjust to the
new workflow.
Could you make "push -v" a bit more verbose ? I initially forgot to
rebase and couldn't see the error message from the remote. I guess this
also means that the current code will hide messages from hooks such as
changes made to Bugzilla.

Cheers,

Louis

[Tim Harder]

On 2021-02-27 Sat 19:04, Louis Sautier wrote:
> Could you make "push -v" a bit more verbose ? I initially forgot to rebase
> and couldn't see the error message from the remote. I guess this also means
> that the current code will hide messages from hooks such as changes made to
> Bugzilla.

Should now be fixed in git.

[Tim Harder]

On 2021-02-27 Sat 07:50, Tim Harder wrote:
> 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.

Just wanted to follow up that an initial release is in the tree
providing commit support (pkgdev commit), manifesting (pkgdev manifest),
and push support (pkgdev push).

If you're missing your favorite commit-related repoman option please
open an issue. What's mainly still missing are good docs explaining
usage and workflow.

Thanks,
Tim