public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] pkgdev: an alternative to `repoman commit`
Date: Sat, 27 Feb 2021 15:22:22 +0000	[thread overview]
Message-ID: <0B8ADCC8-B50C-4126-92F6-2453EB2C6C62@gentoo.org> (raw)
In-Reply-To: <YDpcI5pAVxB5yFcU@fir>

[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]



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

> 
> Thanks,
> Tim
> 
> [1]: https://github.com/pkgcore/pkgdev
> 


[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

  reply	other threads:[~2021-02-27 15:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-27 14:50 [gentoo-dev] pkgdev: an alternative to `repoman commit` Tim Harder
2021-02-27 15:22 ` Sam James [this message]
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=0B8ADCC8-B50C-4126-92F6-2453EB2C6C62@gentoo.org \
    --to=sam@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