From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 0F9D215808B for ; Thu, 10 Mar 2022 22:04:27 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7FD94E09BF; Thu, 10 Mar 2022 22:04:21 +0000 (UTC) Received: from smtp.gentoo.org (mail.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 12F56E0919 for ; Thu, 10 Mar 2022 22:04:21 +0000 (UTC) From: Sam James Content-Type: multipart/signed; boundary="Apple-Mail=_E16F4D67-BC1E-438A-92D3-C5924A2E6427"; protocol="application/pgp-signature"; micalg=pgp-sha512 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\)) Subject: Re: [gentoo-dev] Deprecating repoman Date: Thu, 10 Mar 2022 22:04:06 +0000 References: <87k0d2x0wy.fsf@gentoo.org> <29e67b7a-5d91-bca6-b686-1ea1008bbcd8@gentoo.org> To: gentoo-dev@lists.gentoo.org In-Reply-To: <29e67b7a-5d91-bca6-b686-1ea1008bbcd8@gentoo.org> Message-Id: <8A335941-A1B6-4B6D-95DC-9CB0F6BD75A0@gentoo.org> X-Mailer: Apple Mail (2.3693.60.0.1.1) X-Archives-Salt: d0a45e49-f99b-4b00-8760-a7322f36aa30 X-Archives-Hash: 970078d08c353da9f92338b52fe9172a --Apple-Mail=_E16F4D67-BC1E-438A-92D3-C5924A2E6427 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On 10 Mar 2022, at 21:57, Joshua Kinard wrote: >>=20 >> I'd be interested in hearing your workflow, so we can capture it in >> the table (mentioned earlier) so its clear how your existing workflow >> will work with the new tools (or perhaps there is a gap, or we need = to >> craft / add additional tools?) I agree on the face it may not be >> obvious what workflows look like. >=20 > My workflow is really rather standard when working in the tree itself. = I > work one package directory at a time, apply changes that I've tested = outside > of the tree in my local repo, eyeball everything a second time to make = sure > I didn't miss something, regenerate the manifest, git add, run = 'repoman full > -d -x', fix any issues it finds (if any) and manifest/git add again, = then > 'repoman commit' and supply a commit message with sign-off. Lather, = rinse, > repeat for other packages. >=20 Having the same checks applied as in CI (which affects whether changes are deployed to users too) is important. pkgcheck has more checks than = repoman. --Apple-Mail=_E16F4D67-BC1E-438A-92D3-C5924A2E6427 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEYOpPv/uDUzOcqtTy9JIoEO6gSDsFAmIqddZfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYw RUE0RkJGRkI4MzUzMzM5Q0FBRDRGMkY0OTIyODEwRUVBMDQ4M0IACgkQ9JIoEO6g SDtldAgAuB2RX0dcWmqzaxDsk4MiWhRbcChmT3fguLTyT3NQ5bPLl47faMgY/bSN +RQCmhzRk6zJWgTSczn1EhjRAMsJv8fXTT+fwWw27e2908EqctW6/gO+2w08a6uz rIggY0l5RcHSoywA7DLeF2WG620UDY5PKTXr5x8nw7HQLNizOsoAF4pswuQh2B7A dEjx1lJ//+TbwUz5v0Zsh/201+6dWyVlj1aGqL1rmbBLuZgkJYTZr4gEy+DD8CvI bPcVwFv3eooewP16ILSobTaWHlce4HwoXtooouZ8BG7TJQwITBl+25bsHO2C/b4T JzFUMuk0uI3KIg3BE48LakNNIyUfpA== =Hsuk -----END PGP SIGNATURE----- --Apple-Mail=_E16F4D67-BC1E-438A-92D3-C5924A2E6427--