A bit confused on why it's too late to change the directory structure for the 3.5 release. Does the location that it is installed to have the potential to affect the stability of FDO?<div><br></div><div>If the concern is that there are other products that are counting on the current install location of fdo under Linux, then there's certainly the option for those products to have their own builds of FDO. We could even create a custom branch / sandbox for this purpose if desired, but I don't think that this should constrain us from making this kind of change. I don't think we've even started the beta process yet?<div>
<br></div><div>Jason<br><div><br><div class="gmail_quote">On 18 February 2010 11:06, Greg Boone wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi All,<br>
<br>
One point of interest. Such directory name changes would have to be applied to the trunk. It is too late to get these types of changes applied to the official release of 3.5.0. In that light, we can bump up the proposed directory to fdo-3.6.0 or I am open to suggestions.<br>
<font color="#888888"><br>
Greg<br>
</font><div><div></div><div class="h5"><br></div></div></blockquote></div></div></div></div>