2010/12/20 Igor Stasenko <span dir="ltr"><<a href="mailto:siguctua@gmail.com" target="_blank">siguctua@gmail.com</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
On 20 December 2010 02:09, Hernán Morales Durand<br>
<div><<a href="mailto:hernan.morales@gmail.com" target="_blank">hernan.morales@gmail.com</a>> wrote:<br>
> Yes, or locate it in a directory and/or copy to the current one. By<br>
> the way, it could be configured a location for just having only one<br>
> sources file?<br>
<br>
</div>+1 . it would be nice to be able to specify a system-wide location for<br>
.sources files,<br>
so any image could look for them at this place first than looking at<br>
current directory.<br></blockquote><div><br>First the sources are searched at the vmPath, then at the imagePath and finally at the defaultPath (which could be the same as the imagePath, see [1]).<br>On Unix the vmPath will be no option for a central directory to hold the sources files, because it's usually /usr/bin, unless you have installed your vm locally in your home directory.<br>
I think it would be nice to have a vm SystemAttribute to hold the sources path. This could be defined during installation, overridden by .ini files, command line switches, props or whatever and always default to vmPath if no other info is available. But the reception for this change wasn't so good as far as I remember, maybe mainly because the issue isn't so pressing while running on Windows/MacOS (or that everything that defines the concept of having a sources file should be completely on the image side).<br>
<br>Alex<br><br>[1] FileDirectory class openSources: fullSourcesName forImage: imageName<br></div></div>