public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Hank Leininger <hlein@korelogic.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Deprecating repoman
Date: Sat, 12 Mar 2022 12:21:29 -0700	[thread overview]
Message-ID: <20220312115421.e635cde5-b6a2-403d-9ce8-ae9772e00dd2@korelogic.com> (raw)
In-Reply-To: <YixayIDhxXD07xyo@gentoo.org>

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

> On 11-03-2022 13:19:34 -0800, Matt Turner wrote:
> > I've filed a PR against devmanual.git to remove references to repoman
> > and replace them with references to pkgdev where appropriate.

On 2022-03-12, Fabian Groffen wrote:
> 
> Just wondering, is there a "migration guide" or something?  I've never
> used pkg* since joining in 2005.  I can derive some things from the
> first look at the below commit, but an "expert opinion" to just map the
> standard things from repoman to appropriate commands would be nice.

Yes, please this, and not just in devmanual, but also:

  https://www.gentoo.org/glep/glep-0066.html
  https://wiki.gentoo.org/wiki/Gentoo_git_workflow
  https://wiki.gentoo.org/wiki/Gentoo_GitHub

All three of those mention repoman some or a lot, and pkgcheck/pkgdev
little or none.

I'm not a dev, just a forgetful proxy maintainer. When I went to learn
the right workflow to submit better-quality PRs on GitHub instead of
just attaching patches to b.g.o. bugs some years back, I looked at
devmanual but the git workflow specific content seemed to be targeted
only at people with access to git.gentoo.org, so I looked elsewhere.

Those Wiki pages talked specifically about my use case. I think they
only mentioned repoman back then. Even now they are 10x more specific
and detailed about how to use repoman in your workflow, vs how to use
pkgcheck.

And indeed, the devmanual still doesn't line up 1:1 with the apparently
soon-to-be-obsolete content in the wikis. For example, wikis say to use
"repoman -dx full"; devmanual only talks about "repoman full" and
replacing that with "pkgcheck scan --commits". What happened to
--include-dev and --xmlparse? Are they not needed/implied in the
pkgcheck case? (From its manpage, I think maybe the default behavior is
equivalent to enabling both of those, but...?)

This is why you can't trust ignorant fools like me to figure it out for
ourselves :-P

Thanks,

-- 

Hank Leininger <hlein@korelogic.com>
9606 3BF9 B593 4CBC E31A  A384 6200 F6E3 781E 3DD7

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-03-12 19:21 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 21:00 [gentoo-dev] Deprecating repoman Matt Turner
2022-03-09 21:14 ` Rich Freeman
2022-03-09 21:19   ` Matt Turner
2022-03-09 21:37     ` Matthias Maier
2022-03-09 21:47       ` Matt Turner
2022-03-09 22:33         ` Matthias Maier
2022-03-09 23:32           ` Matt Turner
2022-03-10  0:17             ` Matthias Maier
2022-03-10  0:51               ` Matt Turner
2022-03-10 18:28         ` Joshua Kinard
2022-03-10 19:44           ` Andreas K. Huettel
2022-03-10 21:53             ` Joshua Kinard
2022-03-10 22:00               ` John Helmert III
2022-03-10 19:59           ` Alec Warner
2022-03-10 21:57             ` Joshua Kinard
2022-03-10 22:04               ` Sam James
2022-03-09 21:23 ` Brian Evans
2022-03-09 21:25 ` Ionen Wolkens
2022-03-19  4:43   ` Zoltan Puskas
2022-03-19  7:15     ` Ulrich Mueller
2022-03-19  8:48       ` Michał Górny
2022-03-09 21:25 ` Anna Vyalkova
2022-03-09 21:27 ` Maciej Barć
2022-03-09 21:28   ` Matt Turner
2022-03-09 21:32     ` Brian Evans
2022-03-09 21:45       ` Matt Turner
2022-03-10  7:09 ` Joonas Niilola
2022-03-10 17:29   ` Matt Turner
2022-03-10 18:07     ` William Hubbs
2022-03-10 18:22       ` John Helmert III
2022-03-11  7:30       ` Anna Vyalkova
2022-03-11 16:49       ` Brian Dolbec
2022-03-11 17:14     ` Peter Stuge
2022-03-11 18:25       ` Alec Warner
2022-03-11 19:04         ` Brian Dolbec
2022-03-11 19:51         ` Joshua Kinard
2022-03-11 20:11           ` Arthur Zamarin
2022-03-12  1:45           ` Sam James
2022-03-12  1:54       ` Sam James
2022-03-10 18:27 ` Joshua Kinard
2022-03-10 19:58   ` Alec Warner
2022-03-10 23:18     ` Joshua Kinard
2022-03-11  8:54       ` Mart Raudsepp
2022-03-11 19:39         ` Joshua Kinard
2022-03-12  1:54           ` Sam James
2022-03-12  2:17             ` Joshua Kinard
2022-03-12  1:57       ` Sam James
2022-03-12  2:53         ` Joshua Kinard
2022-03-12 10:37           ` Mart Raudsepp
2022-03-11 19:38     ` Ulrich Mueller
2022-03-11 21:19 ` [gentoo-dev] " Matt Turner
2022-03-12  8:33   ` Fabian Groffen
2022-03-12 19:21     ` Hank Leininger [this message]
2022-03-12 20:26   ` Matt Turner
2022-03-13 22:52     ` Matt Turner
2022-03-12  0:43 ` [gentoo-dev] " Francesco Riosa
2022-03-12  0:46   ` Matt Turner

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=20220312115421.e635cde5-b6a2-403d-9ce8-ae9772e00dd2@korelogic.com \
    --to=hlein@korelogic.com \
    --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