On 05/03/2013 01:44, Dimitar Zhekov wrote:
On Sun, 3 Mar 2013 10:37:21 +1100 Lex Trotman elextr@gmail.com wrote:
Great minds think alike. :) However, as Colomban stated, making it a core plugin means that it will be a compile-time option for the whole Geany package, which is no different from making it a compile-time-only option for Geany itself.
Sure but if compiled into binary packages, the plugin will still not load if libvte isn't present on the end user system. So we have the same flexibility as now. A binary distro would only not compile it in if it didn't even have VTE available in its repos at all.
You are right, as Loong Jin also pointed out. All we need to do is drop a note to the package maintainers not to add libvte as run-time dependency, just in case. Neither build nor run time dependencies need to be changed, which is a good thing.
It's worth noting that not adding libvte as a runtime dependency may actually be pretty hard to implement, as at least on Debian, some of the dependencies are inferred from the NEEDED entries (objdump -p) of ELF binaries and shared objects. I believe rpmbuild also does something similar for RH-based distros.
I'd suggest splitting the terminal plugin into a separate, recommended (optional, installed by default) package instead.