ceterum censeo... we need really should get rid of the .sources and .changes implementation. (one of the things I want for 3.0... and I am sure all the people who now say "how unimportant" will be amazed what this will get us...) Marcus On Nov 22, 2012, at 6:38 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:

Hi,

the packages for Linux distribution have troubles to work with *.sources files. Currently the image is looking for sources files in this order: - vm directory - image directory - working directory There are packages for the virtual machine and the image. All in latest versions. The sources file should be part of the image package. But in that case it must copy the sources file into the VM location (and that may be complicated because of version string in the vm path). In case that you update the image package and the image uses newer sources version, the old one should be deleted. There are several more or less bad solutions: - copy the sources file next to the image and changes file when the new custom image is being created. Very space consuming - create symlink next to the image and changes file. Bad because in case you update image package the old source file is deleted - collect all old source files in the vm package. Bad because you do not know what image version will be used - collect all old source files in the image package. Very strange and you have to place the sources files somehow next to the virtual machine - have standalone package for every source file and place symlinks next to the image file when a new custom image is created

So as you may see, we really need some next way how to resolve sources files location. In ideal world we would be able to read it from a system variable. The user will have in his home all source files that images he owns use. But we do not have VM support for that.

Cheers, -- Pavel

-- Marcus Denker -- http://marcusdenker.de