Created attachment 435156 [details] scite-3.6.5.ebuild with gtk3 default support A new upstream release available. I suggest attached ebuild which uses gtk3+ as default and switch to gtk2+ vie the gtk2 useflag for the portage tree. From the announce-mail: SciTE 3.6.6 is a bug fix release concentrating on GTK+. The SciTE_USERHOME environment variable allows setting a separate location for writable properties files. Other changes were made and bugs fixed. A detailed list of changes is available on the history page. http://www.scintilla.org/ScintillaHistory.html Thanks to the contributors of code and documentation and to the testers. Neil From the changelog: Released 24 May 2016. C++ 11 <regex> support built by default. Can be disabled by defining NO_CXX11_REGEX. SciTE_USERHOME environment variable allows separate location for writable properties files. Feature #965. GObject introspection supports notify and command events. The Progress lexer now allows comments preceded by a tab. Scripts reading Scintilla.iface file include comments for enu and lex definitions. Bug #1829 . Fix crashes on GTK+ if idle work active when destroyed. Bug #1827. Fixed bugs when used on GTK+ 3.20. Bug #1825. Bug #1831. Fix SciTE search field background with dark theme on GTK+ 2.x. Bug #1826. Fixed bug on Win32 that allowed resizing autocompletion from bottom when it was located above the caret. On Win32, when using a screen reader and selecting text using Shift+Arrow, fix bug when scrolling made the caret stay at the same screen location so the screen reader did not speak the added or removed selection. Ervin
Created attachment 435270 [details] scite-3.6.6.ebuild with gtk3 default support when using gnome This ebuild uses gtk+3 as default when gnome is set and gtk2 is not set. when gnome is not set then it uses gtk+2.
Created attachment 435486 [details] scite-3.6.6.ebuild with gtk2/3 support and gtk3 default Se bug #583204. as described there it is no good idea to use the gnome useflag. SO it is best to support gtk+2 via the gtk2 useflag and use gtk3 as default, as described to the gtk useflags. ervin
Created attachment 435578 [details] scite-3.6.6.ebuild updated removed einfo "using gtk?" messages and moved emake_pars to src_compile to avoid the global variable
Created attachment 439754 [details] scite-3.6.6.ebuild without gtk+ choice, using gtk+-3 Due to the ongoing debate about semantik and use of the gtk2 useflag I removed it completely and set the gtk+-3 dependency. Hope that's enough to get it in the tree.
FWIW to get ebuilds and eclasses highlighted I use: file.patterns.portage=*.ebuild;*.eclass lexer.$(file.patterns.portage)=bash I just append it to SciTEGlobal.properties, but maybe it could go in its own portage.properties file. That could then even be further developed.
We're at V 3.7.2 now. Renaming the ebuild works fine. ervin
It's 3.7.5 now: http://www.scintilla.org/SciTE.html Version 3.7.5 adds Reverse Selected Lines and Select All Bookmarks commands. Version 3.7.4 restores performance on GTK+. Version 3.7.3 fixes problems with GTK+ on Wayland. . . . http://www.scintilla.org/SciTEDownload.html points to . . . http://www.scintilla.org/scite375.tgz Downloading attachment "scite-3.6.6.ebuild without gtk+ choice, using gtk+-3" , copy-renaming and adapting . . . SRC_URI="http://www.scintilla.org/${PN}${MY_PV}.tgz" just WORKSFORME . @ Ervin Peters : Anything objecting getting updates into Main Portage Tree ? POSTSCRIPTUM: . . . "Bug 593542 - app-editors/scite-3.6.7 - Version bump" seems to be DUPLICATE or OBSOLETE by now.
(In reply to Manfred Knick from comment #7) > POSTSCRIPTUM: > > . . . "Bug 593542 - app-editors/scite-3.6.7 - Version bump" > > seems to be DUPLICATE or OBSOLETE by now. Same seems to apply to . . . "Bug 583204 - app-editors/scite-3.6.5-r1 with gtk3 Support as default" .
Hallo, we're at 4.0.0 now. The ebuilds work fine, but unfortunately still none proxy-maintainers did decide, which on to use in tree. (I'm only proxy-maintained) I'm unlucky 'bout that. For myself I created a script 'scite-update.sh' which runs on the local tree: #! /bin/bash ev=$1 if [ $ev ] ; then . /etc/portage/make.conf sdir="/usr/local/portage/app-editors/scite" cd $sdir eb=`ls -1r "scite-"*".ebuild" | head -n 1` echo echo "Upgrading $eb to Version $ev" echo cp $eb "scite-$ev.ebuild" echo "$eb nach scite-$ev.ebuild kopiert" chown -R portage.portage $sdir cd pushd $sdir repoman manifest popd emerge -av scite scite & else echo echo "So geht's: $0 \$Version" echo fi Yes, the other bugs are mainly obsolete, but there are relevant comments posted. Ervin
(In reply to Ervin Peters from comment #9) Danke! Thanks a lot! Hint: One might need to adapt the directory - in my case, it is . . . /usr/local/portage/local-overlay/app-editors/scite .........................^^^^^^^^^^^^^..................
obsolete, up2date ebuild provided in Bug #593542 ervin
