The GTK2 version of sylpheed claws is finaly 'released' (well, for testing at least ...) Just copied and pasted together an ebuild, it works, i know its not the cleanest way to do it, but well ... A (nameing) problem i run into is that the plugin versions for maildir and pgpinline havend changed, but this plugins compile against gtk2 and not anymore against 1.2 (of course) ... so for me (and now) I just incremented the release version. Its the first ebuild, so don't be to hard ;) Hoping an GTK2 sylpheed-claws gets into portage. Reproducible: Always Steps to Reproduce:
Created attachment 54889 [details] Sylpheed-Claws-1.9.6 ebuild
Created attachment 54890 [details] Maildir ebuild for Sylpheed-Claws-1.9.6
Created attachment 54891 [details] pgpinline ebuild for Sylpheed-Claws 1.9.6
Well, there is already a gtk2 ebuild in the tree based on a cvs snapshot: 1.0.1.1 Still thinking how to handle the plugins and if I should SLOT it or not.
If you decide to SLOT plugins, you will need to patch claws so gtk2 version will look into different directory. It is currently not possible via configure, as confirmed by Paul.
Ticho: You know, I read that mail from Colin too ;)
Created attachment 54934 [details] Sylpheed-Claws-1.9.6 ebuild Has been late yesterday, just some minor things, but there shouldn't be any comments inside of multiline depends ...
Well, I was talking to Paul on IRC.
Don't know if it possible and useful, but couldn't we just 'patch' the plugins in case sc-1.9.6 or up is installed? As long as the plugins have the same version numbers fior gtk1 and gtk2 versions one of the versions could imho be considered 'just' a patch.
Will there be a Sylpheed-Claws-GTK2 ebuild in the portage tree anytime soon? According to the posts in this thread http://sourceforge.net/mailarchive/forum.php?thread_id=7066857&forum_id=2006 the GTK2 branch is now considered the main branch, with GTK1 being in maintenance mode only.
I, for one, would quite like to see this in Portage. Can we make a decision on this?
1.9.9 is out now. Here's a modified version of the ebuild that works on amd64 and ppc. I've replaced the version specific SRC_URI with one using ${P}.
Created attachment 58476 [details] Updated ebuild for sylpheed-claws-1.9.9
Thanks. Seems to be working nicely for me.
Created attachment 58531 [details] Sylpheed-Claws-1.9.9 ebuild Hi, well didn't work for me, first of all mesh doesn't seem to have the package online yet (but the switch mirror does). Second, nice to change the hard-coded path, but you missed a "sylpheed-claws" in the path, as ${P} just contains the Package-Name. The Attached Ebuild has just this two changes, and works for me, so I hope i works for everyone else too. Also works together with the two plugin ebuild from above.
Yeah sorry, I forgot to mention that I had to tinker with it a bit first. Been a long day.
ok, 1.9.9 in cvs. Will deal with the plugins in the next days.
Sorry about the path thing, I'm sure it worked when i tested it. For some reason, I wasn't added to the cc list on this bug, so I wasn't aware of your comments. Anyway, 1.9.11 is out now, fixing the spell checker problems. Renaming the 1.9.9 ebuild works.
I test Sylpheed-Claws-1.9.9 ebuild on a ppc. It compiles and works fine. Maybe add the keyword ~ppc to the ebuild (I did this to test the ebuild)
