| 1 |
On 20-05-22 16:17:20, Joonas Niilola wrote: |
| 2 |
> If you have no plans to keep on contributing, but want to test just one |
| 3 |
> change/ebuild, you can do that in a local overlay and by prepending |
| 4 |
> those settings to your emerge once. Setting up a chroot, container/etc |
| 5 |
> is time-consuming and in my opinion not worth it for a single package. |
| 6 |
> However if you intend to keep on writing ebuilds, then go for it, but |
| 7 |
> bear in mind you have then two "systems" to keep updated. |
| 8 |
Hopefully I will be able to make time to continue to contribute, that is the plan anyway :-). I have a spare machine for my |
| 9 |
personal tests that I keep up to date or reinstall anyway ^^. |
| 10 |
|
| 11 |
> You may also be interested in dev-python/ebuildtester for random |
| 12 |
> occassional, but thorough testings. |
| 13 |
Thanks, I overlooked this one. |
| 14 |
|
| 15 |
> > 1- download stage3, unpack it in /mnt/gentoo |
| 16 |
> > 2- chroot in /mnt/gentoo |
| 17 |
> > 3- emerge --sync, select stable profile default/linux/amd64/17.1 |
| 18 |
> > 4- update the @world set |
| 19 |
> > 5- add to make.conf the variables from https://wiki.gentoo.org/wiki/Package_testing (with multilib-strict added to FEATURES) |
| 20 |
|
| 21 |
> Note that if you plan on keeping the chroot alive, these will become |
| 22 |
> your default settings when you update @world, or emerge dependencies. |
| 23 |
> Which will most likely become a painful road. |
| 24 |
That would have been my second question. I tried that, and had to add |
| 25 |
tons of '-test' to package.use to get dev-python/quantities to be merged due to circular dependencies of several dev-python/? packages. |
| 26 |
|
| 27 |
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) |
| 28 |
|
| 29 |
> I have a "testmerge.sh" shell script that runs "emerge -1av --onlydeps |
| 30 |
> --with-test-deps "$@"", then sources a different make.conf (with |
| 31 |
> stricter FEATURES etc) before running "emerge -1av "$@"". |
| 32 |
Thanks for the tip. I am also writing some bash scripts to automate the overall process :-) |
| 33 |
|
| 34 |
> Overall sounds good. |
| 35 |
Thanks, I'll test that and post the relevant parts on https://wiki.gentoo.org/wiki/Chroot_for_package_testing |
| 36 |
|
| 37 |
Best regards, |
| 38 |
David. |
Archives