New 0.7.0 version of goldendict is now out Reproducible: Always
Created attachment 187088 [details] goldendict ebuild
Created attachment 187100 [details] goldendict ebuild with ~amd64 keyword add ~amd64 keyword
Created attachment 187102 [details] app-dicts/goldendict-0.7.0.ebuild Hello. I added missed DEPEND and ~amd64 keyword. Also some polishing.
Created attachment 189335 [details] ebuild for 8.0 This ebuild does not solve or workaround problem with "ld: cannot find -llibhunspell.so" error I think, it's better to fix hunspell ebuild to solve this problem.
(In reply to comment #4) > Created an attachment (id=189335) [edit] > ebuild for 8.0 > > This ebuild does not solve or workaround problem with > "ld: cannot find -llibhunspell.so" error > > I think, it's better to fix hunspell ebuild to solve this problem. > please do not post ebuilds for 0.8 version here, more over do not post not workable ebuild
Created attachment 189346 [details] app-dicts/goldendict-0.8 [x] virtual/stardict provided [x] corrected dependencies [x] hunspell fix [x] support for myspell's ebuilds [x] support for russian addon TODO: [ ] support for stardict's dictionaries ebuilds [ ] eapi=2
Created attachment 189348 [details] app-dicts/goldendict svn live ebuild same as 0.8 but live
why exactly we should not post ebuilds for new versions of software which is under active development (say alpha) and bug-fixing ? opening separate reports for every version seems kinda redundant
Created attachment 189354 [details] goldendict-0.8.0.ebuild Updated to 0.8.0. I know, this package contain russian localization, but currently .pro file no have support for l10n framework, so better ask upstream fix this first.
agreed. but just in case if you were talking about "russian addon" there and not that separate issue of inappropriate translation since its not present in your ebuild - i meant 4 additional dictionaries and speech module by this words by the way: .pro file also need correct installation data. do's and inst's is no good. i think it's all be taken care of soon. what did we want from 3rd public release after all ?
*** Bug 267369 has been marked as a duplicate of this bug. ***
Created attachment 189493 [details] app-dicts/goldendict universal 0.8.0 and live [X] EAPI=2-ready [F] trying to put stardict's dicts in DEPEND in any way was a bad idea, hell with it [-] questionable virtual/stardict removed
Created attachment 189494 [details] app-dicts/goldendict universal 0.8.0 and live [*] fix incomplete src_unpack. sorry
Created attachment 192391 [details] goldendict 0.9.0 ebuild
Created attachment 192408 [details] app-dicts/goldendict-0.9.0 and live [x] support for some more morphologic addons from upstream (optional) [x] support selective localization installations [!] not builds with gcc-4.4.0
Created attachment 192483 [details] goldendict-0.9.0.ebuild 0.9.0 I still dislike to include all stuff from upstream to one ebuild, better split package to app and dictionary.
0.9.0 ebuild added to qting-edge overlay for testing
Created attachment 205119 [details, diff] gcc-4.4-fix.patch Please add this patch to solve problem compiling with gcc-4.4
Thanks, gcc-4.4 patch added to the overlay :)
Created attachment 207216 [details] app-dicts/goldendict-0.9.0 [A] added gcc-4.4 patch support [U] updated EN<->RU pack [A] added morphology for fr,it,es,pt_BR from upstream
there is no much point to put additional stuff from upstream on standard places for dictionaries in gentoo because we, probably, have better morphology in portage already, licensing terms for those from upstream are unclear and i don't know better place to put voice pack than one proposed by upstream for all of their stuff. this is purely a lazy-man option and i will cut it out later.
Will this ebuilds be at portage? Or some overlay maybe?
(In reply to comment #22) > Will this ebuilds be at portage? Or some overlay maybe? layman -a qting-edge
Thank you. Also, where I can get live ebuild? 0.9.0 have segfault trouble with Qt 4.5.3. Someone on forums advised upgrade to live version.
It segfaults with 4.6.0 too
Created attachment 213483 [details] goldendict ebuild via git
new live (9999) ebuild was added due to goldendict was moved to git instread of svn, as well it segfaults on qt 4.6
> as well it segfaults on qt 4.6 as well it FIX segfaults on qt 4.6 - so, now it works ok
The live git ebuild should be reviewed and put in the overlay. Then I'd like a snapshot to be made for inclusion in portage.
On tree now. I am gonna review the live ebuild and put it on the overlay Thanks
Compiling of live version failes here.
(In reply to comment #31) > Compiling of live version failes here. > Ehh, this can happen with live ebuild... PS: logs, emerge --info etc?
Created attachment 217665 [details] --info file
Created attachment 217666 [details] installation output --info file and installation output attached. Yes, I was tryed live version because of 0.9.0 crashes with my qt.
(In reply to comment #34) OK, I think this is because live version now require x11-libs/qt-phonon, but there little funny block with kde-base/phonon-kde, so I cannot install this package and check it.
(In reply to comment #35) > (In reply to comment #34) > > OK, I think this is because live version now require x11-libs/qt-phonon, but > there little funny block with kde-base/phonon-kde, so I cannot install this > package and check it. > placing corrent includes fixes build for me, goldendict works smoothly)
(In reply to comment #36) > (In reply to comment #35) > > (In reply to comment #34) > > > > OK, I think this is because live version now require x11-libs/qt-phonon, but > > there little funny block with kde-base/phonon-kde, so I cannot install this > > package and check it. > > > > placing corrent includes fixes build for me, goldendict works smoothly) > Can you explain how to get it working?
(In reply to comment #37) > (In reply to comment #36) > > (In reply to comment #35) > > > (In reply to comment #34) > > > > > > OK, I think this is because live version now require x11-libs/qt-phonon, but > > > there little funny block with kde-base/phonon-kde, so I cannot install this > > > package and check it. > > > > > > > placing corrent includes fixes build for me, goldendict works smoothly) > > > > Can you explain how to get it working? > here comes the patch --- src/goldendict.pro.orig 2010-02-04 13:06:57.000000000 +0300 +++ src/goldendict.pro 2010-02-04 13:07:46.000000000 +0300 @@ -10,7 +10,6 @@ QT += webkit QT += xml QT += network -QT += phonon CONFIG += exceptions \ rtti \ stl @@ -44,6 +43,7 @@ vorbis \ ogg \ hunspell + INCLUDEPATH += /usr/include/KDE LIBS += -lX11 \ -lXtst PREFIX = $$(PREFIX) and addition to the ebuild: src_prepare() { epatch "${FILESDIR}/phonon-live.patch" } it definitely breaks windows build, but who cares?)
(In reply to comment #38) > + INCLUDEPATH += /usr/include/KDE We don't want no stinkin' KDE includes. Using /usr/include/phonon/ should be enough.
(In reply to comment #39) > (In reply to comment #38) > > + INCLUDEPATH += /usr/include/KDE > > We don't want no stinkin' KDE includes. Using /usr/include/phonon/ should be > enough. > as you wish :-P, just in case compare actual contents of /usr/include/phonon/ /usr/include/KDE/Phonon/ and take a look at subj sources ;)
Well, I don't really care, such a patch should be put behind a kde useflag. Ideally upstream should make it work with both Qt's as well as KDE's Phonon.
Can someone explain what "enruen" pack is?
(In reply to comment #42) > Can someone explain what "enruen" pack is? > This is en-ru and ru-en dictionaries from upstream. Generally useless for average user. Also license status for me still unclean.
(In reply to comment #43) > (In reply to comment #42) > > Can someone explain what "enruen" pack is? > > > > This is en-ru and ru-en dictionaries from upstream. Generally useless for > average user. Also license status for me still unclean. > And why aren't myspell dictionaries enough? Btw, I just pushed an almost rewritten goldendict-9999 live ebuild to qting-edge overlay, without all those addons. Please test it.
> Btw, I just pushed an almost rewritten goldendict-9999 live ebuild to > qting-edge overlay, without all those addons. Please test it. You cutted off nls support, please return nls USE-flag with src_configure statement: src_configure() { if use nls; then lrelease goldendict.pro || die "lrelease failed" fi PREFIX=/usr eqmake4 } Program runs without errors.
(In reply to comment #45) > > Btw, I just pushed an almost rewritten goldendict-9999 live ebuild to > > qting-edge overlay, without all those addons. Please test it. > > You cutted off nls support, please return nls USE-flag with src_configure > statement: > I know, that's why it's still a work in progress... ;-) Your proposed fix is wrong though. Translations are already generated, the problem is that they're not installed.
We have a working ebuild now in the official overlay. This bug can be considered as fixed.
what is the "official overlay" ?
Sergey, /usr/portage goldendict-0.9.0_p20100410.ebuild added.
(In reply to comment #48) > what is the "official overlay" ? > layman -a qting-edge
is it a final answer or just another guess ? :) first of all, nor i nor gentoo-portage.com [http://gentoo-portage.com/app-dicts/goldendict] could find this "goldendict-0.9.0_p20100410.ebuild" but only "goldendict-0.9.0.ebuild". but it doesn't matter since summary says "app-dicts/goldendict live ebuild" which they both are, probably, not. second, since when "portage" is called an "official overlay" and is it ? and since when answer on question "what" is <how to add some obscure stuff to my system> ? you can ignore that since i've reread top of the bug and in my understanding it is in some overlay with high concentration of official gentoo developers where it kinda supposed to boil until it becomes less "edgy". guess that makes it "official" but this term kind of new to me. and to some of you, probably, too.
(In reply to comment #51) > is it a final answer or just another guess ? :) The answer Davide gave (he's a member of our Qt team) is correct. The Gentoo Qt team maintains the qting-edge overlay. It is therefore "official". http://qt.gentoo.org/ also mentions the qting-edge overlay. > first of all, nor i nor gentoo-portage.com > [http://gentoo-portage.com/app-dicts/goldendict] could find this > "goldendict-0.9.0_p20100410.ebuild" but only "goldendict-0.9.0.ebuild". gentoo-portage.com is not an official gentoo website, so it is probably just not up to date. http://packages.gentoo.org/package/app-dicts/goldendict does show the snapshot ebuild I committed earlier. > but it doesn't matter since summary says "app-dicts/goldendict live ebuild" > which they both are, probably, not. indeed they are not > second, since when "portage" is called an "official overlay" and is it ? No, it is "the official tree" and not referred to as an overlay. > in my understanding it > is in some overlay with high concentration of official gentoo developers > where it kinda supposed to boil until it becomes less "edgy". A live ebuild should not be included in the portage tree, in our view it belongs in an overlay. As the qting-edge overlay is maintained by the same Gentoo developers, with the help of some users (I must say very capable ones), you can be assured of the same ebuild quality. But as it is "live" code you are dealing with, we cannot give any guarantees as to how it will work at any given time.