On 20-05-22 16:17:20, Joonas Niilola wrote:
> 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.
Hopefully I will be able to make time to continue to contribute, that is the plan anyway :-). I have a spare machine for my
personal tests that I keep up to date or reinstall anyway ^^.

> You may also be interested in dev-python/ebuildtester for random
> occassional, but thorough testings.
Thanks, I overlooked this one.

> > 1- download stage3, unpack it in /mnt/gentoo
> > 2- chroot in /mnt/gentoo 
> > 3- emerge --sync, select stable profile default/linux/amd64/17.1
> > 4- update the @world set 
> > 5- add to make.conf the variables from https://wiki.gentoo.org/wiki/Package_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.
That would have been my second question. I tried that, and had to add 
tons of '-test' to package.use to get dev-python/quantities to be merged due to circular dependencies of several dev-python/? packages. 

In doing that I remarked that tests for python3.7 fails with '/dev/tty : No such device or address'. Am I missing something before chrooting ? (I did follow https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Base before chrooting)

> 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 "$@"".
Thanks for the tip. I am also writing some bash scripts to automate the overall process :-)

> Overall sounds good.
Thanks, I'll test that and post the relevant parts on https://wiki.gentoo.org/wiki/Chroot_for_package_testing

Best regards,
David.