On Wed, Apr 02, 2008 at 05:01:29PM -0500, Bo Peng wrote: > > > > > > _This_ surely won't ever work outside controlled enviroments. > > > > > > > > > > > Yes, I think that's precisely what he's trying to do. He wants to be able > > to have a single (say) image file that is embedded in multiple LyX files, > > referenced by absolute path, and have it be packed and unpacked, etc, etc, > > to and from some shared location. But don't take my word for it. > > Your understanding is correct. In this particular case, maybe Andre > refers to ../images/blah, which is relative and easier to handle, but > this does not really matter.
Well, in any case, that's a fundamental ownership problem here. Who is allowed to delete files outside the bundle? > The current implementation allows you to embed *any* file, relative or > absolute. Once they are embedded, they should work in the embedded > mode. If you unbundle them under the same system, they went back to > their original locations. (Note that, because these out-of-tree files > are relatively stable, overwrite is usually not needed). When we > unbundle them on another system, we try to put them to the same > location, but this can be impossible due to OS differences. This is > where all the discussions start. I'd simply drop that feature. There is no proper solution possible. Actually, when I think about it... Suppose I bundle a file with relative path "../../../../../../../../../etc/passwd" and open that file with root permissions in LyX. What would happen? Andre'
