Date: Mon, 07 Nov 2022 22:36:42 +0100 From: Nicolas Herry <beastieboy@beastieboy.net> To: Fernando =?utf-8?Q?Apestegu=C3=ADa?= <fernando.apesteguia@gmail.com> Cc: User Questions <freebsd-questions@freebsd.org> Subject: Re: Testing ports of rust software w/o building rustc Message-ID: <86bkpiih05.fsf@beastieboy.net> In-Reply-To: <CAGwOe2amkTGbbT-kUUBG0woQeP7obBZ8eJV0zHhSUuJL%2BQ-iRA@mail.gmail.com> ("Fernando =?utf-8?Q?Apestegu=C3=ADa=22's?= message of "Mon, 7 Nov 2022 21:54:10 %2B0100") References: <86h6zajyd0.fsf@beastieboy.net> <CAGwOe2amkTGbbT-kUUBG0woQeP7obBZ8eJV0zHhSUuJL%2BQ-iRA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Fernando Apestegu=C3=ADa <fernando.apesteguia@gmail.com> writes: > Is there a way to avoid having to build rustc and yet test the port in > isolation, to be sure I've captured all the dependencies? Or is there > something I'm missing here I should be doing? > > Try to configure poudriere not to use many parallel jobs. Also try not to= put too many things in tmpfs. Everything else has been built, only rust was left (as it takes literally hours to build...), so I had only one job running then. > Additionally you could try poudriere-devel since it has the ability to do= wnload packages if they are present in the package > repository instead of rebuilding them. Ah-ha! I need to look into that! Sounds almost too good to be true! > I really enjoy the moment when it downloads llvm, GCC, rustic, cmake, etc= :-) :)=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86bkpiih05.fsf>