On 03-Mar-13 01:51, Joao Luis Meloni Assirati wrote:
This seems a fair use case. Note that if the symlink does not exist, a hierarchy of directories is created automatically by dpkg to accommodate the files, and the installation process will not explicitly fail.
It doesn't fail - that's correct. However, the base package (which is an installer for closed-source development files) won't put the symlinks in the right place (and *will* fail, since I use the -T option in the script), so it will not function as intended.
Therefore, the solution of a package that creates symlinks that serve as filesystem structure for other packages is not very "robust", as symlinks are easily removable (by administration errors).
Yeah, that's what happens when you try and deal with closed-source header files that use brain-damaged directory structure and try and get them to play nice with standard build tools....
Thanks for your help. I guess I'll just have to put the requirement for a pre-depends somewhere in the documentation :( It's ugly, but it works.