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

[Louis Sautier <sbraz@gentoo.org>]

[-- Attachment #1.1: Type: text/plain, Size: 1822 bytes --]

On 27/02/2021 15:50, Tim Harder 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.
> 
> 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
> 

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


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]