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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id B4B441382C5 for ; Fri, 22 May 2020 13:17:34 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E477AE089F; Fri, 22 May 2020 13:17:33 +0000 (UTC) Received: from smtp.gentoo.org (dev.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 92D84E089F for ; Fri, 22 May 2020 13:17:33 +0000 (UTC) Subject: Re: [gentoo-proxy-maint] Testing environment To: gentoo-proxy-maint@lists.gentoo.org References: <20200522061710.GA6290@captain-america> From: Joonas Niilola Message-ID: Date: Fri, 22 May 2020 16:17:20 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Proxy Maintainers X-BeenThere: gentoo-proxy-maint@gentoo.org X-BeenThere: gentoo-proxy-maint@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 In-Reply-To: <20200522061710.GA6290@captain-america> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="6F3mjMbGbk2tCWFuiB2DsbTpzEO4MdYLB" X-Archives-Salt: 8bd51b3c-67c4-4574-833b-c19fbe18b3e0 X-Archives-Hash: 405e097924aa51b20976051dcd566afe This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --6F3mjMbGbk2tCWFuiB2DsbTpzEO4MdYLB Content-Type: multipart/mixed; boundary="kNLlaKLiffANHePpLJwCfOC3maY26RhMG" --kNLlaKLiffANHePpLJwCfOC3maY26RhMG Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US Hey, On 5/22/20 9:17 AM, David Denoncin wrote: > Dear all, > > I would like to understand how to set up an acceptable testing environm= ent for amd64 packages as per > https://wiki.gentoo.org/wiki/Package_testing > > and would like to go the chroot way. Is the following setup acceptable > to test an ebuild for pkg-cat/pkg-name ? If you have no plans to keep on contributing, but want to test just one change/ebuild, you can do that in a local overlay and by prepending those settings to your emerge once. Setting up a chroot, container/etc is time-consuming and in my opinion not worth it for a single package. However if you intend to keep on writing ebuilds, then go for it, but bear in mind you have then two "systems" to keep updated. You may also be interested in dev-python/ebuildtester for random occassional, but thorough testings. > > 1- download stage3, unpack it in /mnt/gentoo > 2- chroot in /mnt/gentoo=20 > 3- emerge --sync, select stable profile default/linux/amd64/17.1 > 4- update the @world set=20 > 5- add to make.conf the variables from https://wiki.gentoo.org/wiki/Pac= kage_testing (with multilib-strict added to FEATURES) Note that if you plan on keeping the chroot alive, these will become your default settings when you update @world, or emerge dependencies. Which will most likely become a painful road. I have a "testmerge.sh" shell script that runs "emerge -1av --onlydeps --with-test-deps "$@"", then sources a different make.conf (with stricter FEATURES etc) before running "emerge -1av "$@"". > 6- emerge portage with the gentoo_dev use flag=20 > 7- emerge pkg-cat/pkg-name (ebuild test) > 8- runtime test the package if needed > > I'm happy to amend the above checklist however appropriate and > contribute to the wikipage related to chroot. > > Thanks in advance, > Best regards, > David Denoncin. Overall sounds good. -- juippis --kNLlaKLiffANHePpLJwCfOC3maY26RhMG-- --6F3mjMbGbk2tCWFuiB2DsbTpzEO4MdYLB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGnBAEBCgCRFiEEltRJ9L6XRmDQCngHc4OUK43AaWIFAl7H0OBfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDk2 RDQ0OUY0QkU5NzQ2NjBEMDBBNzgwNzczODM5NDJCOERDMDY5NjITHGp1aXBwaXNA Z2VudG9vLm9yZwAKCRBzg5QrjcBpYhMNCACtGnyyVRFPI4StwHkGVTOeY/Ii0ve9 E5C+/bFHyem0SnOSCQn2z3UezAyITIOt3OxizRpgwvXHXbk3BDXE8qtnZPHz9rTx EtIThVIjQTUceFWWq1yTyZIOli3iwq+L03Xn91CZA9SjBj0gbxb9plEBYTeXBmcD ZQcJxBCNOgobLFgToxakKlIJLxqksD7BcojUbaH1RGFRWosgyXcP1mW9snDVT7WO IAS9BpXwh/lWsVDUp4MlhmHRlnEQxxwEgQV8axEFUkE5gID8nAxkdblR0JbwN1rs 5/hgoZ7FDhP7HJ/CYxKX6Xb4Z1/ckZakff/nj5dTRFw5L8PSu8qLOoZB =pPMQ -----END PGP SIGNATURE----- --6F3mjMbGbk2tCWFuiB2DsbTpzEO4MdYLB--