On 10/06/2013 04:39 PM, Ingo Weinhold wrote:
The various git components only use relative paths to refer to each other (or probably, rather to the core components), so git can be installed anywhere. While this is nice, breaking git up into different packages means they have to be installed in the same installation location or otherwise won't find the files they depend on.
But, in the case of git, is that really a problem? Why should it be in system in the first place? It sounds pretty optional to me, at least.
But even if you have another software in mind that uses this method, and where it makes sense to break it up into pieces, and which happens to be installed in system: if it requires common-badbadsoftware or system-badbadsoftware instead of badbadsoftware, where is the problem assuming common-badbadsoftware somehow manages to hide/override system-badbadsoftware?
It's also something that very likely cannot be upstreamed, i.e. has to be maintained forever.
[...]
So I'd be very careful with any feature that requires additional changes in ported software.
That point of view certainly makes sense, although I wouldn't introduce too many compromises because of it (like getting rid of find_directory(), or adopting a more Unix like directory scheme to ease porting efforts).
Bye, Axel.
