<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 21, 2016 at 12:33 PM, R P Herrold <span dir="ltr"><<a href="mailto:herrold@owlriver.com" target="_blank">herrold@owlriver.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On Tue, 21 Jun 2016, R P Herrold wrote:<br>
<br>
> but ... I think you re overthinking this ... why not use a<br>
> tool such as 'mock' to build inside a chroot running the older<br>
> version?<br>
<br>
</span>I see by your later post that you anticipate needing to test<br>
within a richer environment than just a build space. </blockquote><div><br></div><div>Yes, <font color="#232323" face="Arial">I want to be "immersed" in the target environment -- using native versions of applications for the actual development environment, testing, etc.; having "man" pages show the right thing for that version; allowing multiple users to be in the same space at the same time (for group debugging, etc.); have ports and other kernel resources disjoint from the host; run legacy versions of services/daemons; etc. </font></div></div><br></div></div>