I wanted to ask if there is enough interest to get scintilla unbundled out of several apps (anjuta, geany, scite, ...) into its own package. There is at least one report about bundeled scintilla in app-text/silvercity: https://bugs.gentoo.org/show_bug.cgi?id=383327 === background: I wanted to try textadept. The most natural approach for me is to write ebuilds for the package and its dependencies. The first dependency I had to tackle was scintilla. Turned out to be a big mess. Hand-crafted Makefiles for the components. And even worse it builds only a static lib. Upstream on static vs. dynamic libs: http://sourceforge.net/p/scintilla/feature-requests/555/ I have not too much knowledge about Makefile-writing. So getting patches that upstream might accept would get a painful task for me ;) I then went on and looked at textadept buildsystem. Again - just a Makefile. Even worse it expects all its dependencies (scintilla, lpeg and what not) being present as source (!) in its src directory and then builds it. Great. I now use the prebuilt binary - and think I even don't like it enough to take the burden to create patches and ebuilds. But I think it might be a good idea to get at least scintilla into its own package - hence this report.
So you want this to be a tracker bug for packages bundling scintilla?
(In reply to Jeroen Roovers from comment #1) > So you want this to be a tracker bug for packages bundling scintilla? Yes. But there also needs to be a discussion on how to achieve this. As already mentioned upstream expects applications to use the static lib or entirely bundle scintilla. Unbundling would get tricky if applications use modified versions or arbitrary hg-checkouts. But even if it is impossible it can be good to track those packages if there once should be a security issue, so patches can get applied to the affected bundled versions.
