Beagle reasles is out, searching and a whole lot more. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Sorry forgot to attach URL, http://www.gnome.org/projects/beagle. This may be assigned to the wrong section as it is nto the same app-sci/beagle.
You can find cvs ebuilds on breakmygentoo.net, but IMO these ebuils are not very stable.
I think this issue should be assigned to gnome@gentoo.org, as this beagle is defintely not identical to app-sci/beagle.
Poke 0.4 is out now Any word on this at least getting properly assigned and added to portage?
Well, I guess this one should go to gnome. I'm not in gnome herd, but I would like to take care of it and suggest gnome-extra/beagle ? kai
afaic this still very much alpha quality software and as such should be p.mask-ed if it has to enter the tree (but i guess its too hyped up to get around that sooner or later). kzimmerman : post an ebuild here so we can see how it works out.
Created attachment 49050 [details] beagle-0.0.4.ebuild Well this ebuild is a fix on this bug. However, several things have to be considered: 1. Beagle needs a running DBUS session, that means we are touching 77504 here. 2. Beagle has a lot of nice extra features that are not included in the proposed ebuild. 3. The code seems to be stable but in my opinion it needs too much memory. 4. A lot of stuff has to be done to get Beagle to work (kernel options, DBUS, Beagle daemon). I fear we won't be able to automate this. kai
Created attachment 49344 [details] beagle-0.0.4.ebuild There has been a typo. Also, there is now support for the evolution-sharp extension. I decided to use the "evo" USE flag, but I'm open for other suggestions. latexer: If I see it right you have already done some work on this stuff (beagle, evolution-/gsf-/gst-sharp)? kai
As I said, there are a lot of extensions that we should take care of... kai
This is really more dotnet than gnome, all of the dependencies are handled by the dotnet herd.
* evo USE flag should be eds, plus that it's a cvs snapshot, so i wouldn't work with that as this point. * no configure time switch for the eds flag, bad. * there is a fair amount of duplication in the ebuild. * it misses RDEPS for sure. * why does it dep sharp on one dbus version, declarded like this it won't even take revision bumps. * why is there commented out code ? * the xattr part doesn't mention you need kernel support, only the inotify part does and that doesn't necessarily coincide. @ obz : don't turn the dotnet herd into a second gnome herd.
> * evo USE flag should be eds, plus that it's a cvs snapshot, so i wouldn't work with that as this point. Could be done in a later release, maybe we should send this upstream. > * no configure time switch for the eds flag, bad. I know, but the configure autodetects if the *-sharp stuff exists. > * there is a fair amount of duplication in the ebuild. I guess you mean the "built_with_use ... mono" stuff? Well, I thought this would make it more clear to the user, but I could change that... > * it misses RDEPS for sure. I don't know of any that I missed, but I may be terrible wrong at this point. > * why does it dep sharp on one dbus version, declarded like this it won't even take revision bumps. My mistake :) > * why is there commented out code ? Because its still in devlopment...and I will change that, too. > * the xattr part doesn't mention you need kernel support, only the inotify part does and that doesn't necessarily coincide. I will add a sentence.
Created attachment 49370 [details] beagle-0.0.4.ebuild I don't like diffs here, so again a complete version :) kai
@foser: almost every dependency is handled by the dotnet herd - doesn't it make sense? at least until we herd by function.
Almost all of those deps are CVS, or rely on CVS things to function. So if you folks choose to throw this over to dotnet@g.o, you'll get a big old "RESOLVED LATER" from it. I've been following beagle for a while now. It's pretty neat stuff, but just not ready for general use/portage at this point.
Created attachment 49493 [details] beagle-0.0.4.ebuild This one includes some fixes (thanks foser): 1. eds USE flag 2. sqlite 2.X API 3. no autodetection anymore kai
Created attachment 49494 [details, diff] beagle-0.0.4-configure.in.patch
Beagle 0.0.5 is out! Regarding the ebuild/patch nothing has changed. Rename it and it will work with 0.0.5, too. kai
Created attachment 49642 [details] beagle-0.0.5.ebuild As you may see, there is still a lot of work to be done.. 1. Now we have the mozilla-extension installed in /usr/share/beagle (based on mozilla use flag). However, the user has to run firefox -install-global-extension /usr/share/beagle/beagle.xpi manually. Hopefully there will be a solution sometime to get this done from inside the ebuild. 2. I think I found out why foser had such a problem with my autoconfiguration-patch. I mixed enable/disable, it still worked because I made the mistake twice:) 3. I also put some work into the mozilla-backend and epiphany-extension (46486) but without any results for this ebuild. kai
Created attachment 49643 [details, diff] beagle-0.0.5-configure.in.patch
* about the patch : i just looked at it, never tested it. I still it doubt it does in all cases exactly what we want, but your ebuild is incomplete in that respect, it uses the old 'myconf trick' instead of use_enable like you really should. * It uses einstall instead of 'make DESTDIR' like it really should. * I don't really see the point of the mozilla flag, is it really harmful to just install the thing by default. Does it really only work with firefox/mozilla, not with other mozilla variants ? * imo lots of text is still redundant & rather incomplete (eg. your mozilla extensions stuff sais nothing about what user should install the extension) * you point to a wiki that is not gentoo specific... don't let ppl mess up their config files because you said it was ok to do stuff that is said there. * i bet it still misses buildtime deps. * you do inherit nsplugins, but does it get used ? * you do inherit gnome2 eclass, but actually override all of its functionality. You shouldn't be overriding stuff without a good reason (and I don't think you have here).
Created attachment 49665 [details] beagle-0.0.5.ebuild > * about the patch : i just looked at it, never tested it. I still it doubt it does in all cases exactly what we want, but your ebuild is incomplete in that respect, it uses the old 'myconf trick' instead of use_enable like you really should. Ok, here comes my second guess what you mean. My patch works only if --enable-evolution is set (what I did in the ebuild). It won't work with use_enable because both --enable/--disable will result in actication? I changed that and will continue with guessing :) And of course it uses use_enable now... > * It uses einstall instead of 'make DESTDIR' like it really should. Done > * I don't really see the point of the mozilla flag, is it really harmful to just install the thing by default. Does it really only work with firefox/mozilla, not with other mozilla variants ? About the mozilla flag: I'm not so shure whats Gentoo typical at this one. Its not harmful to install, but maybe people wan't only what they ordered? Anyway, its gone now. About other mozilla variants: I guess everything that supports mozilla extensions (tested only firefox and mozilla). > * imo lots of text is still redundant & rather incomplete (eg. your mozilla extensions stuff sais nothing about what user should install the extension) Please be more specific or change what has to be changed. However, I reduced the text a bit. > * you point to a wiki that is not gentoo specific... don't let ppl mess up their config files because you said it was ok to do stuff that is said there. Didn't know that this is Gentoo policy. Anyway, the HOMEPAGE="XXX" stuff should be enough. > * i bet it still misses buildtime deps. We will see :) > * you do inherit nsplugins, but does it get used ? Not anymore, gone now. > * you do inherit gnome2 eclass, but actually override all of its functionality. You shouldn't be overriding stuff without a good reason (and I don't think you have here). Well, I used the eclass because its such a nice solution for the URL=".." thing. But you are right, I should use the whole thing...done. I guess beagle will become part of gnome someday :) @foser: Again, thanks for your help. I'm still learning a lot :) kai
Created attachment 49666 [details, diff] beagle-0.0.5-configure.in.patch
Is it possible to build beagle against Mozilla Firefox instead of the Mozilla Suite? If so, could the dependency on net-www/mozilla be changed in such a way that net-www/mozilla and net-www/mozilla-firefox provide a virtual/gecko and beagle depends on that?
@24: Argh, stupid me. Only after submitting did I see that it is dev-dotnet/gecko-sharp that depends on net-www/mozilla. But the same reasoning stands for dev-dotnet/gecko-sharp's dependency.
No, you can't. There's a bug marked WONTFIX for gecko-sharp about this. Firefox is *not* an SDK, they make no claims that they won't change things in firefox, etc, etc. Mozilla is a browser *AND* an SDK. There's no changing that any time soon. gecko-sharp *might* build against firefox with some gross hacking, but there's no assuring that the next minor firefox release won't completely hork things. Sorry to be curt, but we get requests for this all the time, and I love firefox as much as the next man/woman, but it's *not* a replacement for the SDK portion of things.
When I'm trying to search it crashes :( $ beagle-query gimp (<unknown>:22496): Gdk-WARNING **: locale not supported by Xlib (<unknown>:22496): Gdk-WARNING **: cannot set locale modifiers file:///home/genady12/cxoffice/changelog.txt file:///usr/share/applications/gimp-2.0.desktop file:///usr/share/applications/gimp-2.1.desktop *** glibc detected *** free(): invalid pointer: 0x081ea000 *** /usr/bin/beagle-query: line 13: 22496 Aborted MONO_GAC_PREFIX="/usr:$MONO_GAC_PREFIX" MONO_PATH="$THIS_PATH:$MONO_PATH" BEAGLE_FILTER_PATH="$BEAGLE_FILTER_PATH:$THIS_FILTERS" mono --debug $MONO_EXTRA_ARGS $THIS_EXE "$@" $ best (best:22404): Gdk-WARNING **: locale not supported by Xlib (best:22404): Gdk-WARNING **: cannot set locale modifiers Qt: Locales not supported on X server Rendering Done Rendering: .33s SetSource: Rendering Done Rendering: .12s Rendering Done Rendering: .11s Rendering Unhandled Exception: System.NullReferenceException: A null value was found where an object instance was required. in (unmanaged) (wrapper managed-to-native) Gtk.Application:gtk_main () in <0x00004> (wrapper managed-to-native) Gtk.Application:gtk_main () in <0x00007> Gtk.Application:Run () in <0x00007> Gnome.Program:Run () in [0x0007f] (at /var/tmp/portage/beagle-0.0.5/work/beagle-0.0.5/Best/Best.cs:92) Best.Best:Main (string[]) *** glibc detected *** free(): invalid pointer: 0x0875b000 ***
*** Bug 79931 has been marked as a duplicate of this bug. ***
Why it's not at portage?
I did everything OK, and it seems to work fine. Finds DBUS and all, but on every query both with beagle-query and best, I get: The query failed with error: DBus.DBusException: Message did not receive a reply in [0x0005d] (at /var/tmp/portage/dbus-0.23-r1/work/dbus-0.23/mono/Message.cs:205) DBus.Message:SendWithReplyAndBlock () in <0x0007c> Beagle.Factory.Proxy:NewQueryPath () in [0x00005] (at /var/tmp/portage/beagle-0.0.5/work/beagle-0.0.5/BeagleClient/Factory.cs:52) Beagle.Factory:NewQuery () in [0x00005] (at /var/tmp/portage/beagle-0.0.5/work/beagle-0.0.5/tools/Query.cs:160) QueryTool:Main (string[]) free(): invalid pointer 0x80187000! What could that be? a bug in dbus?
Created attachment 50200 [details] beagle-0.0.5.ebuild Small changes in the deps (this include gmime-2.1.11 that is currently not in protage) and einfos. kai
i tried this out on my system install wasnt to bad setup was a bit painfull since the kernel patch is required perhaps due to the fact im running nptl on glibc it eats all my memory and swap when it starts indexing so adding a warning might be suggested to the ebuild or perhaps just completely stop when nptl is enabled fyi i used a mono 1.1.3 ebuild i found and it didnt help any ether also isnt having packages in portage called the same thing a no-no? cause portage already has sci-libs/beagle...
from my experience, it works with mono-1.0.4-r1 from portage perfectly, but if you have a system with nptl, you must compile mono with nptl, which means to compile it with gcc-3.4. Also - do you use by any chance the Inotify path version 0.18 ? If you do that might cause memory problems, as beagle-0.0.5 needs Inotify 0.17 . Inotify 0.18 is for Beagle CVS Hope that helps to anyone
.18 is prob my problem then silly me thinking it would be backwards compatable... i dont feel like rebooting any more for now so ill prob just wait for 0.0.6 unless a patch is back ported from cvs
No problem, even though that's a really easy patch, and beagle is lovely :)
$ beagle-query asdasdas *** glibc detected *** free(): invalid pointer: 0x081e6000 *** /usr/bin/beagle-query: line 13: 14993 Aborted MONO_GAC_PREFIX="/usr:$MONO_GAC_PREFIX" MONO_PATH="$THIS_PATH:$MONO_PATH" BEAGLE_FILTER_PATH="$BEAGLE_FILTER_PATH:$THIS_FILTERS" mono --debug $MONO_EXTRA_ARGS $THIS_EXE "$@"
my old 100 lire i found out that in my home directory i got a link [Transgaming stuff] pointing to /usr/share/blabla, beagled crashed all the times in that point [rights stuff?] ... removing that link i got it work, now my indexing process keeps on browsing through the other folders and best can seek everything a nerd like me wants to find
It seem that I need >=dev-libs/gmime-2.1.11. Where can I get this?
tried to do a version bump of gmime from 2.1.10 to 2.1.11. Seems to compile ok.
gmime-2.1.11 should be in portage already - just emerge sync :-)
dbus got bumped in portage to dbus-0.23-r3, and keyworded x86. The only problem is that once dbus is upgraded, beagle no longer works (and also does not compile anymore)...
dbus got bumped in portage to dbus-0.23-r3, and keyworded x86. The only problem is that once dbus is upgraded, beagle no longer works (and also does not compile anymore)... downgrading back to dbus-0.23-r1 fixes the problem.
This is not actually a real problem. dbus had to get rid of mono support to become stable. Well, beagle needs the mono support of dbus. foser don't like this litle fellow anyway, so I guess he decided that getting dbus stable is more important than beagle :) kai
mono support removed from dbus? I didn't notice anything unstable with mono support in dbus. In any case - shouldn't there be at least a version with mono support which is keyworded and has a higher version figure? That way if I have dbus in package.keywords I can easily have mono support... That makes sense to me more than marking the latest stable dbus in p.masked and then using the keyworded one...
Beagle 0.0.6 is now available at http://ftp.gnome.org/pub/GNOME/sources/beagle/0.0/beagle-0.0.6.tar.gz
Created attachment 51333 [details] beagle-0.0.6.ebuild This is the ebuild for 0.0.6. It depends on debus-0.23.1 that is not in portage yet. kai
Hopefully we will also get mono support back :) kai
A comment about the deps: #79300 : This is evolution support for beagle #77504 : Well, whenever beagle goes to protage we need a user friendly solution for a dbus session. #81794 : Right now we need dbus-0.23.1 with mono support enabled. kai
Created attachment 51351 [details] Some changes to beagle-0.0.6.ebuild 1. beagle depends on >=net-www/mozilla-1.6 for gtkmozembed (or firefox/thunderbird, but these don't currently have gtkmozembed in Portage). 2. All the g*-sharp deps should be strict e.g. =dev-dotnet/gnome-sharp-1.0*. An issue if, like me, you have gtk-sharp-1.9.x and derived g*-sharp installed. 3. Suggest use flags and deps for mozilla, network, epiphany, msoffice. Later gstreamer and zeroconf, when their respective deps have been released.
Created attachment 51352 [details, diff] beagle-0.0.6-configure.in.patch
Also: need to add dep >=dev-libs/atk-1.2.4 as this is not implied by any existing deps (at least not directly).
scratch that, we do depend on atk indirectly and 1.6.1 is lowest version in portage. my bad.
Created attachment 51361 [details] beagle-0.0.6.ebuild Network support is currently broken. Note also that epiphany support will fail as it wants epiphany-1.2; not much we can do about this atm.
Well, right now network, epiphany and msoffice does not work and that is the reason why it was not included in my proposed ebuild. kai
Created attachment 51503 [details] beagle-0.0.6.1.ebuild This is version 0.0.6.1 of beagle. Does not look as stable as 0.0.5 was, but you should try it by yourself. I included also ed's suggestion about the mozilla dep for gtkmozemb (thanks ed). You can use the existing configure patch. kai
Beagle-0.0.6.1 seems to work much much better with mono-1.1.4 rather than 1.0.5. First I don't get the crashes I got with 1.0.5, and second - it hardly ever reaches the 62MB mem limit, which is broken ith 1.0.5 every 2-3 secs :) at least I didn't notice it with 1.1.4 anymore. I really suggest using mono-1.1.4 with beagle-0.0.6.1. It should soon be in portage. Mono-1.0.6 is already in portage, I'm not sure if it works as well as 1.1.4 (I would guess not...) but you might test and report :)
dbus 0.23.2 is out Change Log: * fix a bug in the mono bindings in which non-deterministic class finalization could cause dbus errors at application shutdown * a ton of thread locking-related bugs fixed * enforce that apps speaking on the session bus are the same user as the bus itself
Please look at: #82657 dev-dotnet/mono-1.1.4 #82656 sys-apps/dbus-0.23.2
yes you posted the same changelog thrice now, will you please stop spamming.
RE: comment #58, maybe this should act as a tracker bug and other bugs related to beagle and its dependancies should be added to dependancies for this bug.
I get this when trying to emerge beagle-0.0.6.1.ebuild, and I used the beagle-0.0.6-configure.in.patch and renamed it to beagle-0.0.6.1-configure.in.patch: configure:20513: checking for gtk-sharp glade-sharp gecko-sharp = 0.6 gnome-sharp dbus-sharp >= 0.23.1 gconf-sharp gmime-sharp >= 2.1.11 configure:20552: error: Library requirements (gtk-sharp glade-sharp gecko-sharp = 0.6 gnome-sharp dbus-sharp >= 0.23.1 gconf-sharp gmime-sharp >= 2.1.11) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them. why is it looking for =0.6, should be 1.0.6 right? Did no one else have this problem?
=0.6 applies to gecko-sharp only, which is correct. You need to find out which pkgconfig package it is failing on; try $ pkg-config --modversion 'gtk-sharp glade-sharp gecko-sharp = 0.6 gnome-sharp dbus-sharp >= 0.23.1 gconf-sharp gmime-sharp >= 2.1.11'
I confirm that using the 0.0.6.1 beagle ebuild + patch from this bug and renaming to 0.0.7 works great. I only found a strange bug so far, causing best to crash only when I search for the keyword 'linux' :)
looks like mono is now in dev-lang/
Created attachment 53262 [details] beagle-0.0.7.ebuild new ebuild for the new version (and integrate the mono's change in portage)
Created attachment 53433 [details] beagle-0.0.7-r1.ebuild added USE-flags "nework" and "epiphany"
Comment on attachment 53433 [details] beagle-0.0.7-r1.ebuild typo, sorry
care to explain what are those USE flags meant to do? the 'epiphany' is rather obvious but not so the 'network'....
Created attachment 53512 [details] beagle-0.0.7-r2.ebuild What the hell brings me to invoke an eds USE-flag?? "epiphany" is the right one.
Created attachment 53513 [details] beagle-0.0.7-r3.ebuild O no, its not my day. Please ignore the ebuild above. The current one is the one you should use :-/
Based on my experience, and the howto at http://forums.gentoo.org/viewtopic.php?t=288526 , 0.0.7 needs >=dev-lang/mono-1.1 Also, I encountered a bug where trying to 'reveal in file manager', would launch nautilus such that it would take over my desktop (managed by xfce). I would imagine this would occur with any environment not that didn't use nautilus for the desktop. Could others verify this? I started a bug over at: http://bugzilla.gnome.org/show_bug.cgi?id=171309
Created attachment 54241 [details] beagle-0.0.7-r4.ebuild I modified line 26 of the ebuild so it looks as follows: epiphany? ( >=www-client/epiphany-extensions-1.6.0 )" rather than epiphany? ( >=net-www/epiphany-extensions-1.6.0 )" because the epiphany-extensions package exists in www-client. After doing this, I was able to emerge beagle w/o a problem.
Comment on attachment 54241 [details] beagle-0.0.7-r4.ebuild epiphany-extensions is in www-client, not net-www
Created attachment 54243 [details, diff] beagle-0.0.7-configure.in.patch Ok, this may be a noob mistake, but I simply copied the beagle-0.0.6-configure.in.patch file and saved it as beagle-0.0.7-configure.in.patch. Everything compiled w/o a problem.
0.0.8 is out
Created attachment 54293 [details] beagle-0.0.8.ebuild Here is an ebuild that I put together and was able to install successfully.
Created attachment 54294 [details] beagle-0.0.8-configure.in.patch Updated patch.
damn..derek beat me to it by 30 seconds. why is this not in portage yet?
From the release announcement: http://mail.gnome.org/archives/dashboard-hackers/2005-March/msg00101.html <snip> DEPENDENCY HECK --------------- Beagle has many dependencies, and thus can be difficult to compile. It requires: * The full Mono stack, including Gtk#. (We all use 1.1.4, and you probably should too, but 1.0.6 will also work. 1.0.5 and earlier will NOT work.) * D-BUS 0.23.4 * Evolution-sharp 0.6 * Gecko-sharp * Gsf-sharp * Gmime 2.1.13 For the best possible Beagle experience, you should also have: * An inotify 0.20-enabled kernel </snip> <snip> KNOWN ISSUES ------------ It doesn't take that much ingenuity to confuse the file system backend. In particular, the right thing doesn't always happen if a file's name changes rapidly. (i.e. "mv foo bar; mv bar baz; mv baz foo") The beagle daemon tends to grow over time, using more and more memory... but we now grow *much* more slowly than previously-released versions. It might need to be periodically killed and restarted. Sometimes the daemon or its associated helper process fail to shut down cleanly. Occasionally you will need to kill a beagle-related process by hand. At this point in development, we cannot commit to stable APIs or file formats. You will almost certainly need to delete your indexes and start again at some point in the future. </snip> It's not stable on 1.0.x, it's got lots of unsatisfied deps (that aren't going to instantly fix themselves), and they developers themselves admit that it's a memory hog, dies, needs restarting, and is not API stable, etc, etc, etc. I have no intention of putting this in til this is more mature. Hurrah for folks like NLD shipping it, they have the people to support it. dotnet herd is mostly a one man show right now, and there's other more pressing, and stable things on my place right now. This bug is a great reference for those wishing to give beagle a try, but I'm not willing to put this in the tree at this time. Hope that helps clear things up. Thanks.
And the folks behind the Beagle project beat out the programmers in Redmond by what ... a few years ;-)
DEPENDS should not have * in them, so for DEPENDS that look like =dev-dotnet/gecko-sharp-0.6*, they should look like >=dev-dotnet/gecko-sharp-0.6 (See http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=3 ) Also, it may be a good idea to update the bug summary to 0.0.8.
@Josh: *DEPENDs with "*" in them are fine, but *only* for =pkg-cat/pkg-version*. The section you refer to mentions not using "*" with >= depends, because >= should specify exactly which version is the minimum to have as a dep. Just wanted to clarify.
">=www-client/mozilla-1.6" is a invalid dependencies!
comment 83: net-www/mozilla was moved to www-client/mozilla in a recent update. Sync and update world.
Ebuilds for 0.0.8 should use >=dev-lang/mono-1.0.6. This is stated in topic on irc, on beaglewiki and it is my own experince as well!
mono-1.0.6 has some threading related problems (for reference, try to run blam for any considerable amount of time using 1.0.6 (blam is thread heavy)) which make it not so suitable for use. I recommend if you're going to bother with beagle, use mono-1.1.x.
Best have some problem with religion :) If I search "Budda", it crashes ... if I search the same string with $ beagle-query budda Not crashes...but maybe I found the problem... There is this result : file:///home/xoen/cefalug/Ơ%20nato il CefaLUG - ZioBudda_files Maybe the problem is the 0%20 char... This is big problem, because best crash every time this result is into the results list :(
Created attachment 54415 [details] beagle-20050325.ebuild CVS ebuild for beagle that supports inotify 21 !
Created attachment 54433 [details] After emerging the beagle-20050325.ebuild, beagled now crashes upon startup. It looks like the daemon is not able to watch/monitor the /home/derek and /usr/share/applications directories.
Like I said: inotify 21 has some API changes so beagle < 0.0.9 wont work with it. 0.0.9 is the next version so I got it from CVS. CVS wont work with inotify 20 !!!
Please stop using this bug as a forum thread. This is _not_ the place for cvs ebuilds (#88), general (non-tree) ebuild problems (#81-#84) nor for offtopic misinformed comments (#80,#78), running into problems with using alpha software (#87,#89) and general information on the pack which is in the README (#90), just to name a few from the bottom of the list. And it is certainly is not the place for people with the inability to read the general instability of the application in between all the fluff comments (#29,#78 -> again, we got a winner).
I tried 0.0.7, the patching was ok. But I couldn't patch beagle-0.0.8.ebuild on my system. This is the info shown in /var/tmp/portage/beagle-0.0.8/temp/beagle-0.0.8-configure.in.patch-25036.out : ***** beagle-0.0.8-configure.in.patch ***** =========================================== PATCH COMMAND: patch -p0 -g0 < /usr/local/got/gnome-extra/beagle/files/beagle-0.0.8-configure.in.patch =========================================== patching file configure.in patch: **** malformed patch at line 9: \ =========================================== PATCH COMMAND: patch -p1 -g0 < /usr/local/got/gnome-extra/beagle/files/beagle-0.0.8-configure.in.patch =========================================== missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- configure.in 2005/02/16 17:05:06 1.1 |+++ configure.in 2005/02/16 17:09:36 -------------------------- No file to patch. Skipping patch. patch: **** malformed patch at line 9: \
Created attachment 54520 [details] beagle-0.0.8.1.ebuild
Created attachment 54521 [details] beagle-0.0.8.1-configure-in.patch
The patching problem still persists in 0.0.8.1 ebuild: ===================================================== These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] gnome-extra/beagle-0.0.8.1 -debug -doc -epiphany +network 0 kB [1] Total size of downloads: 0 kB Portage overlays: [1] /usr/local/got bash-2.05b# ACCEPT_KEYWORDS="~x86" emerge gnome-extra/beagle Calculating dependencies ...done! >>> emerge (1 of 1) gnome-extra/beagle-0.0.8.1 to / >>> md5 src_uri ;-) beagle-0.0.8.1.tar.bz2 * Mono support enabled in sys-apps/dbus, I will continue... * Mono support enabled in dev-libs/gmime, I will continue... >>> Unpacking source... >>> Unpacking beagle-0.0.8.1.tar.bz2 to /var/tmp/portage/beagle-0.0.8.1/work * Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is: * * /usr/local/got/gnome-extra/beagle/files/beagle-0.0.8.1-configure.in.patch * ( beagle-0.0.8.1-configure.in.patch ) !!! ERROR: gnome-extra/beagle-0.0.8.1 failed. !!! Function epatch, Line 260, Exitcode 0 !!! Cannot find $EPATCH_SOURCE! !!! If you need support, post the topmost build error, NOT this status message.
I am not sure if I am doing this right, but I simply renamed beagle-0.0.7-r4.ebuild to beagle-0.0.8.1.ebuild and beagle-0.0.7-configure.in.patch to beagle-0.0.8.1-configure-in.patch, the emerge went smoothly.
Somone can make the ebuild to support beagle web-service? http://www.beaglewiki.org/index.php/Using%20Beagle%20web%2C%20web-service%20access
How should beagled be run? Can we create a /etc/init.d/ script? Or just stick it in my fluxbox startup file?
I've reworked and submitted the configure.in fix here: http://bugzilla.gnome.org/show_bug.cgi?id=172372 Also if nobody objects, I'd like to be the maintainer of this. I'm quite involved in the development at the moment, although I don't feel we are quite ready to get it in portage yet.
Just want to point out, if you are using >=gentoo-sources-2.6.11-r5, you will also need to apply this patch to get the file indexing to work: http://mail.gnome.org/archives/dashboard-hackers/2005-March/msg00078.html
Created attachment 55523 [details, diff] Patch against beagle 0.0.8.1 to add inotify 0.21 support I reformatted the patch from http://mail.gnome.org/archives/dashboard-hackers/2005-March/msg00078.html as a unified diff so it would work with portage. This would have to be added only on some particular kernel versions with inotify 0.21, a rather ugly hack IMO.
Created attachment 55526 [details, diff] beagle-0.0.8.1-inotify-0.21.patch Previous version missed a semicolon, corrected.
just to inform you ... 0.0.9 has been released, sadly bumping does not work since the configure.in patch fails. Well, some autotools guy should be able to fix it withing seconds :D
@Christoph: Actually the patch is not needed anymore thanks to Daniel :) Just remove the line from the ebuild
Created attachment 55862 [details] beagle-0.0.9.ebuild Based on beagle-0.0.8.1.ebuild * Bumped gmime dependency to 2.1.13 * Removed Evolution configure patch
1.) Requires epiphany-1.2, but I have epiphany 1.6 installed (does not find epiphany-1.2.pc and aborts configuration). 2.) No evolution support?
There should be evolution support. Someone took off the "eds" USE flag from IUSE line some time ago, and it never came back, though that USE flag still exists in the ebuild.
The actual epiphany dependency is 1.2 as it fails to build with 1.6 (try this ls -s /usr/lib/pkgconfig/epiphany-1.6.pc /usr/lib/pkgconfig/epiphany-1.2.pc to see what I mean) However, I have seen beagle (0.0.8) running on SuSE 9.3, was able to use RPM to see that thoe only version of epiphany installed was a 1.6.0. Any ideas on how they are doing this? Source RPMS available?
Epiphany is an optional extension. Are you sure they include it in 9.3?
Created attachment 56779 [details] revised beagle-0.0.9.ebuild Dependency on epiphany-1.2* is fixable: sed configure.in and apply a one-line patch (needed anyway, even with epiphany-1.2*). Also corrected IUSE.
Created attachment 56780 [details, diff] beagle-0.0.9-ephy.patch
that works great. Now to create a local user (darn NFS mounted home directories. going to be a major struggle for this tool and extended attributes.)
root@nina root # USE=eds emerge -va app-misc/beagle These are the packages that I would merge, in order: Calculating dependencies - emerge: there are no ebuilds to satisfy ">=dev-dotnet/evolution-sharp-0.6". root@nina root #
Bug 79300, which *is* listed above as a depend.
make[2]: Entering directory `/var/tmp/portage/beagle-0.0.9/work/beagle-0.0.9/Util' wsdl -namespace:Beagle.Util -out:GoogleSearch.cs GoogleSearch.wsdl sed -e "s|\@prefix\@|/usr|g" \ -e "s|\@pkglibdir\@|/usr/lib/beagle|g" \ -e "s|\@pkgdatadir\@|/usr/share/beagle|g" \ -e "s|\@VERSION\@|0.0.9|g" \ -e "s|\@GNOME_PREFIX\@|/usr|g" \ < ./ExternalStringsHack.cs.in > ExternalStringsHack.cs mcs -g -nowarn:0067,0618 --unsafe -o Inotify.exe Inotify.cs Logger.cs -r:Mono.Posix /usr/bin/mono: error while loading shared libraries: libicui18n.so.28: cannot open shared object file: No such file or directory make[2]: *** [GoogleSearch.cs] Error 127 make[2]: *** Waiting for unfinished jobs.... /usr/bin/mono: error while loading shared libraries: libicui18n.so.28: cannot open shared object file: No such file or directory make[2]: *** [Inotify.exe] Error 127 make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/beagle-0.0.9/work/beagle-0.0.9' make: *** [all] Error 2 !!! ERROR: app-misc/beagle-0.0.9 failed. !!! Function gnome2_src_compile, Line 40, Exitcode 2 !!! compile failure -------------------------- locate libicui18n /opt/Ximian-OpenOffice/program/libicui18n.so.22.0 /opt/Ximian-OpenOffice/program/libicui18n.so /opt/Ximian-OpenOffice/program/libicui18n.so.22 /usr/lib/libicui18n.so /usr/lib/libicui18n.so.32.0 /usr/lib/libicui18n.so.32 -------------------------- Where can I get libicui18n.so.28?
revdep-rebuild libicui18n.so.28
That should be # revdep-rebuild --soname libicui18n.so.28 sorry for bugspam.
Created attachment 57489 [details] beagle-0.0.9.ebuild This implements the proper usage of linux-mod to test for inotify support, with a fallback on the running kernel.
The latest ebuild failed on configure because libexif wasn't installed, this should probably be added to the dependencies.
Now epiphanie depends on mozilla or firefox. is it any chance for beagle to accept firefox also ?
Configure also fails for versions of mono less than 1.0.6. This should be added to the dependencies.
Newbie confusion here! I get the following error message when I try to emerge beagle: * Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is: * * /usr/local/portage/app-misc/beagle/files/beagle-0.0.9-ephy.patch * ( beagle-0.0.9-ephy.patch ) I am not sure what I am supposed to patch. Epiphany?
Beagle requires "pdftotext" (xpdf package) to index pdf files. In my opinion it's should be considered as a dependency.
Created attachment 60197 [details] beagle-0.0.10.ebuild (I know its probably a bad candidate for my first ebuild - but I think I did it correctly. Please let me know if I didnt!)
Created attachment 60198 [details] beagle-0.0.10.ebuild First ebuild round 2. ;)
I get this error compiling beagle-0.0.10 make[2]: Entering directory `/var/tmp/portage/beagle-0.0.10/work/beagle-0.0.10/BeagleClient' mcs -debug -nowarn:0067,0618 -out:Beagle.dll -target:library -define:PREFIX=/usr -define:PKGLIBDIR=/usr/lib/beagle ./Client.cs ./Hit.cs ./IIndexableGenerator.cs ./Indexable.cs ./IndexingService.cs ./Message.cs ./Property.cs ./Query.cs ./QueryPart.cs ./QueryResponses.cs ./RemoteControl.cs ./Snippet.cs ./Versioned.cs -r:/usr/lib/mono/gmime-sharp/gmime-sharp.dll -r:/usr/lib/mono/gtk-sharp/glib-sharp.dll -r:/usr/lib/mono/gtk-sharp/pango-sharp.dll -r:/usr/lib/mono/gtk-sharp/atk-sharp.dll -r:/usr/lib/mono/gtk-sharp/gdk-sharp.dll -r:/usr/lib/mono/gtk-sharp/gtk-sharp.dll -r:/usr/lib/mono/gtk-sharp/gconf-sharp.dll -r:/usr/lib/mono/gtk-sharp/gconf-sharp-peditors.dll -r:/usr/lib/mono/gtk-sharp/gnome-sharp.dll -r:/usr/lib/mono/gtk-sharp/art-sharp.dll -r:/usr/lib/mono/evolution-sharp/evolution-sharp.dll -r:Mono.Posix -r:ICSharpCode.SharpZipLib.dll -r:../Util/Util.dll ./Query.cs(70) error CS1501: No overload for method `RegisterAsyncResponseHandler' takes `2' arguments ./Query.cs(70) error CS8006: Could not find any applicable function for this argument list ./Query.cs(71) error CS1501: No overload for method `RegisterAsyncResponseHandler' takes `2' arguments ./Query.cs(71) error CS8006: Could not find any applicable function for this argument list ./Query.cs(72) error CS1501: No overload for method `RegisterAsyncResponseHandler' takes `2' arguments ./Query.cs(72) error CS8006: Could not find any applicable function for this argument list ./Query.cs(73) error CS1501: No overload for method `RegisterAsyncResponseHandler' takes `2' arguments ./Query.cs(73) error CS8006: Could not find any applicable function for this argument list ./Query.cs(74) error CS1501: No overload for method `RegisterAsyncResponseHandler' takes `2' arguments ./Query.cs(74) error CS8006: Could not find any applicable function for this argument list Compilation failed: 10 error(s), 0 warnings make[2]: *** [Beagle.dll] Error 1 make[2]: Leaving directory `/var/tmp/portage/beagle-0.0.10/work/beagle-0.0.10/BeagleClient' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/beagle-0.0.10/work/beagle-0.0.10' make: *** [all] Error 2 !!! ERROR: gnome-extra/beagle-0.0.10 failed. !!! Function gnome2_src_compile, Line 41, Exitcode 2 !!! compile failure !!! If you need support, post the topmost build error, NOT this status message.
(In reply to comment #126) > I get this error compiling beagle-0.0.10 > > ... It compiled without errors after uprading mono to 1.1.7.
Created attachment 60216 [details] beagle-0.0.10.ebuild You forgot the eds USE flag in IUSE and and sqlite as a dependency. xpdf and gnumeric are optinal dependencies, so maybe we should have USE flags for them..?
(In reply to comment #127) > It compiled without errors after uprading mono to 1.1.7. Which version were you using before that?
Looks like it compiles fine for me, but I get a sanbox error: /bin/install -c .libs/libbeagleextension.so /usr/lib/epiphany-1.6/extensions/libbeagleextension.so ACCESS DENIED open_wr: /usr/lib/epiphany-1.6/extensions/libbeagleextension.so/bin/install: cannot create regular file `/usr/lib/epiphany-1.6/extensions/libbeagleextension.so': Permission denied make[2]: *** [install-extensionLTLIBRARIES] Error 1 make[2]: Leaving directory `/var/tmp/portage/beagle-0.0.10/work/beagle-0.0.10/epiphany-extension' make[1]: *** [install-am] Error 2 make[1]: Leaving directory `/var/tmp/portage/beagle-0.0.10/work/beagle-0.0.10/epiphany-extension' make: *** [install-recursive] Error 1 !!! ERROR: gnome-extra/beagle-0.0.10 failed. !!! Function einstall, Line 524, Exitcode 2 !!! einstall failed !!! If you need support, post the topmost build error, NOT this status message. --------------------------- ACCESS VIOLATION SUMMARY ---------------------------LOG FILE = "/tmp/sandbox-gnome-extra_-_beagle-0.0.10-29037.log" open_wr: /usr/lib/epiphany-1.6/extensions/libbeagleextension.so --------------------------------------------------------------------------------
(In reply to comment #129) > Which version were you using before that? 1.0.6
(In reply to comment #130) > Looks like it compiles fine for me, but I get a sanbox error: > > ACCESS DENIED open_wr: > /usr/lib/epiphany-1.6/extensions/libbeagleextension.so/bin/install: cannot Ditto, try to USE="-epiphany"
Replace 'pidof' in /usr/bin/beagled with: ps uxw | grep ssh-agent | grep -v grep | awk '{print $2}' pidof is not available any more
source: http://www-106.ibm.com/developerworks/linux/library/l-keyc3/?Opent=grl,l=929,p=Kp3 of course, replace ssh-agent with something appropriate. I have also submitted a bug upstream at gnome.org.
Also, Beagle 0.0.10 requies mono 1.0.6 or greater. Attached updated ebuild.
Created attachment 60773 [details] beagle-0.0.10-r2.ebuild Updated mono version dependancy to 1.0.6
We no longer need to depend on bug 77504 as 0.0.10 no longer uses DBUS.
(In reply to comment #133) > Replace 'pidof' in /usr/bin/beagled with: > > ps uxw | grep ssh-agent | grep -v grep | awk '{print $2}' > > pidof is not available any more Couldn't we just use /usr/bin/pgrep? It's part of sys-process/procps, so it should be installed on every Gentoo system with maybe the exception of embeded systems.
Hi, I read that beagle can also be queried via http. Could you please add the --enable-webservices in the ebuild?
Oh, forgot my source: http://www.beaglewiki.org/NetworkedBeagleSetup
Updated to version 0.0.11 and added --disable-epiphany-extension-install to config line to fix the sandbox issue. Before, if epiphany was specified at configure time, beagle will try to install the extentions at compile time (GO FIGURE!). Known Ebuild Issue: While epiphany extentions are installed, the files are installed to /usr/lib/epiphany/extensions/ while Gentoo installs epiphany-extentions to /usr/lib/epiphany-1.6/extensions/. Probably need to patch the makefile to find the correct location. I verified the extentions do work by copying them over.
Created attachment 61241 [details] beagle-0.0.11.ebuild Version bump to 0.0.11 and disabled epiphany-extentions install and compile time. (Still installed via portage).
Comment on attachment 60773 [details] beagle-0.0.10-r2.ebuild Updated mono version dependancy to 1.0.6
Build failed on my machine. Here's the output: make all-recursive make[1]: Entering directory `/var/tmp/portage/beagle-0.0.11/work/beagle-0.0.11' Making all in po make[2]: Entering directory `/var/tmp/portage/beagle-0.0.11/work/beagle-0.0.11/po' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/var/tmp/portage/beagle-0.0.11/work/beagle-0.0.11/po' Making all in Util make[2]: Entering directory `/var/tmp/portage/beagle-0.0.11/work/beagle-0.0.11/Util' make[2]: *** No rule to make target `ChmFile.cs', needed by `Util.dll'. Stop. make[2]: Leaving directory `/var/tmp/portage/beagle-0.0.11/work/beagle-0.0.11/Util' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/beagle-0.0.11/work/beagle-0.0.11' make: *** [all] Error 2 emerge info : Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r9 i686) ================================================================= System uname: 2.6.11-gentoo-r9 i686 Intel(R) Pentium(R) M processor 1.70GHz Gentoo Base System version 1.6.12 Python: dev-lang/python-2.3.5 [2.3.5 (#1, Apr 29 2005, 08:52:32)] distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [enabled] dev-lang/python: 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.9.5, 1.7.9-r1, 1.5, 1.8.5-r3, 1.6.3, 1.4_p6 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-Os -mcpu=pentium4 -pipe -fomit-frame-pointer -msse -msse2 -mmmx" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-Os -mcpu=pentium4 -pipe -fomit-frame-pointer -msse -msse2 -mmmx" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distcc distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://www.gigaload.org/gentoo.org/ http://ftp.easynet.nl/mirror/gentoo/" LANG="de_DE.UTF-8" LC_ALL="C" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 S3TC X aalib acpi acpi4linux alsa apache2 apm arts avi bash-completion berkdb bitmap-fonts bonobo bzlib cdr crypt cups curl dbus directfb divx4linux dvd dvdr eds emboss encode esd ethereal evo fam fbcon flac foomaticdb fortran ftp gdbm gif gimpprint gphoto2 gpm gtk gtk2 gtkhtml icq imagemagick imlib java javascript jpeg junit libg++ libwww live lzo mad mikmod mmx mmx2 mono motif moznocompose moznoirc moznomail mozsvg mp3 mpeg nas ncurses network nls ntlm ogg oggvorbis opengl oscar oss pam pcmcia pdflib perl pic png postgres postgresql python quicktime radeon readline real samba sdl slang spell sqlite sse sse2 ssl svg svga tcpd tetex threads tiff truetype truetype-fonts type1-fonts usb vim-with-x vorbis wxwindows xml xml2 xmms xpm xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LDFLAGS, LINGUAS
First time beagle compilation breaks on my laptop (using since 0.5) Used this ebuild, getting and having no clue: arget OS: linux Extended Attributes: libc Prefix: /usr GNOME Prefix: /usr KDE Prefix: /usr/kde/3.4 Evolution-Sharp? yes gsf-sharp? no gst-sharp? no Epiphany Extension? no Mozilla Extension? yes wv1? yes libchm? yes Local SqliteClient? yes Enable WebServices no make all-recursive make[1]: Entering directory `/var/tmp/portage/beagle-0.0.11/work/beagle-0.0.11' Making all in po make[2]: Entering directory `/var/tmp/portage/beagle-0.0.11/work/beagle-0.0.11/po' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/var/tmp/portage/beagle-0.0.11/work/beagle-0.0.11/po' Making all in Util make[2]: Entering directory `/var/tmp/portage/beagle-0.0.11/work/beagle-0.0.11/Util' make[2]: *** No rule to make target `ChmFile.cs', needed by `Util.dll'. Stop. make[2]: Leaving directory `/var/tmp/portage/beagle-0.0.11/work/beagle-0.0.11/Util' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/beagle-0.0.11/work/beagle-0.0.11' make: *** [all] Error 2 Anyone sees the the problem?
(In reply to comment #145) > First time beagle compilation breaks on my laptop (using since 0.5) > Used this ebuild, getting and having no clue: new to bug submitting :) Emerge info: Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.4.3, glibc-2.3.4.20041102-r1, 2.6.11-morph11 i686) ================================================================= System uname: 2.6.11-morph11 i686 Intel(R) Pentium(R) M processor 1.70GHz Gentoo Base System version 1.6.12 Python: dev-lang/python-2.4.1,dev-lang/python-2.3.5 [2.4.1 (#1, Jun 4 2005, 01:52:04)] distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] dev-lang/python: 2.4.1, 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.6.3, 1.9.5, 1.8.5-r3, 1.7.9-r1, 1.4_p6, 1.5 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.11-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=pentium-m -mtune=pentium-m -pipe -O2 -mmmx -msse2 -mfpmath=sse -fomit-frame-pointer -frename-registers -fprefetch-loop-arrays -falign-functions=64" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium-m -mtune=pentium-m -pipe -O2 -mmmx -msse2 -mfpmath=sse -fomit-frame-pointer -frename-registers -fprefetch-loop-arrays -falign-functions=64 -fvisibility-inlines-hidden" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks prelink sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" LDFLAGS="-Wl,-O1 -W1,--enable-new-dtags,--sort-common" LINGUAS="nl" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/portage/main" PORTDIR_OVERLAY="/portage/overlays/bmg-main /portage/overlays/custom-rel /portage/overlays/monostuff /portage/overlays/portage-gentopia /portage/overlays/fluidportage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aalib acpi airo alsa apache2 apm artworkextra audiofile avi bash-completion berkdb bitmap-fonts bonobo cdparanoia cdr crypt cups curl dbus divx4linux dvb dvd dvdr dvdread eds emboss encode esd ethereal exiscan exiscan-acl flac flash foomaticdb fortran gd gdbm gif gnokiii gnome gphoto2 gpm gstreamer gtk gtk+ gtk2 gtkhtml hal ieee1394 imagemagick imap imlib ipv6 java jpeg jpeg2k junit kde lcms ldap libg++ libwww lm_sensors logitech-mouse mad maildir matroska mikmod mmx mmx2 mono motif mozilla moznocompose moznoirc moznomail mozsvg mp3 mpeg mpi mysql ncurses network nls nntp nptl nptlonly nvidia offensive ogg oggvorbis opengl oss pam pcmcia pdflib perl pic png pnp python qt quicktime readline real ruby samba sasl sdl slang slp snmp socks5 spell sqlite sse sse2 ssl svga tcltk tcpd theora tiff truetype truetype-fonts truetype-fontsi type1-fonts udev usb vmf vorbis wifi win32codecs wmf x86 xine xml xml2 xmms xprint xscreensaver xv xvid zlib linguas_nl userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL
Created attachment 61308 [details] beagle-0.0.11-r1.ebuild Looks like I used a previous copy of the ebuild which didn't have the proper mono dependancy. Updated ebuild with correction.
with beagle-0.0.11-r1 I still have this error: Target OS: linux Extended Attributes: libc Prefix: /usr GNOME Prefix: /usr KDE Prefix: unknown; will guess at runtime Evolution-Sharp? yes gsf-sharp? no gst-sharp? no Epiphany Extension? no Mozilla Extension? yes wv1? yes libchm? yes Local SqliteClient? yes Enable WebServices no make all-recursive make[1]: Entering directory `/var/tmp/portage/beagle-0.0.11-r1/work/beagle-0.0.11' Making all in po make[2]: Entering directory `/var/tmp/portage/beagle-0.0.11-r1/work/beagle-0.0.11/po' make[2]: Rien
with beagle-0.0.11-r1 I still have this error: Target OS: linux Extended Attributes: libc Prefix: /usr GNOME Prefix: /usr KDE Prefix: unknown; will guess at runtime Evolution-Sharp? yes gsf-sharp? no gst-sharp? no Epiphany Extension? no Mozilla Extension? yes wv1? yes libchm? yes Local SqliteClient? yes Enable WebServices no make all-recursive make[1]: Entering directory `/var/tmp/portage/beagle-0.0.11-r1/work/beagle-0.0.11' Making all in po make[2]: Entering directory `/var/tmp/portage/beagle-0.0.11-r1/work/beagle-0.0.11/po' make[2]: Rien à faire pour « all ». make[2]: Leaving directory `/var/tmp/portage/beagle-0.0.11-r1/work/beagle-0.0.11/po' Making all in Util make[2]: Entering directory `/var/tmp/portage/beagle-0.0.11-r1/work/beagle-0.0.11/Util' make[2]: *** Pas de règle pour fabriquer la cible « ChmFile.cs », nécessaire pour « Util.dll ». Arrêt. make[2]: Leaving directory `/var/tmp/portage/beagle-0.0.11-r1/work/beagle-0.0.11/Util' make[1]: *** [all-recursive] Erreur 1 make[1]: Leaving directory `/var/tmp/portage/beagle-0.0.11-r1/work/beagle-0.0.11' make: *** [all] Erreur 2 !!! ERROR: app-misc/beagle-0.0.11-r1 failed. !!! Function gnome2_src_compile, Line 41, Exitcode 2 !!! compile failure !!! If you need support, post the topmost build error, NOT this status message.
beagle-0.0.10-r2.ebuild builds on amd64 (gmime is still a pain because of -mono) and seems to work. I suspect that the indexer is skipping various directories for some reason but it doesn't crash (been running the daemon for a week) and you can run queries with it. I believe it's safe to add ~amd64 to the keywords.
(In reply to comment #145) > First time beagle compilation breaks on my laptop (using since 0.5) > Used this ebuild, getting and having no clue: > > arget OS: linux > Extended Attributes: libc > > Prefix: /usr > GNOME Prefix: /usr > KDE Prefix: /usr/kde/3.4 > > Evolution-Sharp? yes > gsf-sharp? no > gst-sharp? no > Epiphany Extension? no > Mozilla Extension? yes > wv1? yes > libchm? yes > > Local SqliteClient? yes > > Enable WebServices no > > make all-recursive > make[1]: Entering directory `/var/tmp/portage/beagle-0.0.11/work/beagle-0.0.11' > Making all in po > make[2]: Entering directory `/var/tmp/portage/beagle-0.0.11/work/beagle-0.0.11/po' > make[2]: Nothing to be done for `all'. > make[2]: Leaving directory `/var/tmp/portage/beagle-0.0.11/work/beagle-0.0.11/po' > Making all in Util > make[2]: Entering directory `/var/tmp/portage/beagle-0.0.11/work/beagle-0.0.11/Util' > make[2]: *** No rule to make target `ChmFile.cs', needed by `Util.dll'. Stop. > make[2]: Leaving directory `/var/tmp/portage/beagle-0.0.11/work/beagle-0.0.11/Util' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/var/tmp/portage/beagle-0.0.11/work/beagle-0.0.11' > make: *** [all] Error 2 > > > Anyone sees the the problem? Looks like you may have app-doc/chmlib installed. Unfortunately, the makefile doesn't allow disabling compilation against that library and I never wrote a make file before, so if you want to test it out and don't need app-doc/chmlib, just remove it... at least until someone figures it out :-D
(In reply to comment #150) > Looks like you may have app-doc/chmlib installed. Unfortunately, the makefile > doesn't allow disabling compilation against that library and I never wrote a > make file before, so if you want to test it out and don't need app-doc/chmlib, > just remove it... at least until someone figures it out :-D Thank you, it was that... I'm in exams period now, so not so much time for doing ebuild and makefile "hacking", but my temporary solution was emerge -C chmlib emerge app-misc/beagle emerge chmlib
(In reply to comment #151) > ebuild and makefile "hacking", but my temporary solution was > emerge -C chmlib > emerge app-misc/beagle > emerge chmlib See the release notes on beagle 0.0.11.1 they fixed this issue, compiled fine on my laptop as is.
having a trouble with beagle-0.0.11-r1.ebuild. emerge is failing with: configure: error: Library requirements (gtk-sharp glade-sharp gecko-sharp = 0.6 gnome-sharp gconf-sharp gmime-sharp >= 2.1.13) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them. did a pkg-config: pkg-config --modversion 'gtk-sharp glade-sharp gecko-sharp = 0.6 gnome-sharp gconf-sharp gmime-sharp >= 2.1.13' Variable 'exec_prefix' not defined in '/usr/lib/pkgconfig/gmime-sharp.pc' my current gmime build is 2.1.14. so it would appear that the ebuild is looking for gmime-sharp when it should be looking for gmime. or perhaps i'm missing a gmime-sharp build somewhere (don't see one in Portage or BMG). any thoughts?
Yeah, you have to add the line: exec_prefix=${prefix} to /usr/lib/pkgconfig/gmime-sharp.pc. The top of the file should look like the following then: prefix=/usr exec_prefix=${prefix} libdir=${exec_prefix}/lib This works (confirmed), but I am not sure where this would be fixed in an ebuild ;)
I don't seem to get beagle compiled on my sysyem. I followed the gentoo-wiki howto in installing beagle, got around the .pc bug in gmime (which is fixed as of today), but am startled by the following compilation error in Tiles: Making all in Tiles make[2]: Entering directory `/var/tmp/portage/beagle-0.0.11-r1/work/beagle-0.0.11/Tiles' mcs -debug -out:Tiles.dll -target:library -warn:4 ./HitFlavor.cs ./HitToHitFlavor.cs ./SimpleRootTile.cs ./Template.cs ./TileActionAttribute.cs ./Tile.cs ./TileBlog.cs ./TileBugzilla.cs ./TileCalendar.cs ./TileCanvas.cs ./TileContact.cs ./TileDocs.cs ./TileFile.cs ./TileFolder.cs ./TileFromHitTemplate.cs ./TileFromTemplate.cs ./TileGoogle.cs ./TileHitCollection.cs ./TileImLog.cs ./TileLauncher.cs ./TileMailMessage.cs ./TileMonodoc.cs ./TileMusic.cs ./TileNote.cs ./TilePicture.cs ./TilePresentation.cs ./TileRenderContext.cs ./TileSpreadsheet.cs ./TileStyleAttribute.cs ./TileWebHistory.cs -r:/usr/lib/mono/gtk-sharp/glib-sharp.dll -r:/usr/lib/mono/gtk-sharp/pango-sharp.dll -r:/usr/lib/mono/gtk-sharp/atk-sharp.dll -r:/usr/lib/mono/gtk-sharp/gdk-sharp.dll -r:/usr/lib/mono/gtk-sharp/gtk-sharp.dll -r:/usr/lib/mono/gtk-sharp/glade-sharp.dll -r:/usr/lib/mono/gecko-sharp/gecko-sharp.dll -r:/usr/lib/mono/gtk-sharp/gnome-sharp.dll -r:/usr/lib/mono/gtk-sharp/art-sharp.dll -r:/usr/lib/mono/gtk-sharp/gconf-sharp.dll -r:/usr/lib/mono/gtk-sharp/gconf-sharp-peditors.dll -r:/usr/lib/mono/gmime-sharp/gmime-sharp.dll -r:../Util/Util.dll -r:../images/Images.dll -r:../BeagleClient/Beagle.dll -r:Mono.Posix -resource:./template-page.css,template-page.css -resource:./template-head.html,template-head.html -resource:./template-foot.html,template-foot.html -resource:./template-contact.html,template-contact.html -resource:./template-file.html,template-file.html -resource:./template-folder.html,template-folder.html -resource:./template-google.html,template-google.html -resource:./template-bugzilla.html,template-bugzilla.html -resource:./template-im-log.html,template-im-log.html -resource:./template-mail-message.html,template-mail-message.html -resource:./template-music.html,template-music.html -resource:./template-note.html,template-note.html -resource:./template-picture.html,template-picture.html -resource:./template-web-history.html,template-web-history.html -resource:./template-blog.html,template-blog.html -resource:./template-monodoc.html,template-monodoc.html -resource:./template-docs.html,template-docs.html -resource:./template-presentation.html,template-presentation.html -resource:./template-launcher.html,template-launcher.html -resource:./template-calendar.html,template-calendar.html -resource:./template-spreadsheet.html,template-spreadsheet.html ./TileMailMessage.cs(78) error CS0117: `GMime.InternetAddress' does not contain a definition for `ParseString' Compilation failed: 1 error(s), 0 warnings make[2]: *** [Tiles.dll] Error 1 make[2]: Leaving directory `/var/tmp/portage/beagle-0.0.11-r1/work/beagle-0.0.11/Tiles' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/beagle-0.0.11-r1/work/beagle-0.0.11' make: *** [all] Error 2 This happens in every emerge attempt, even after re-emerging sqlite, mono, gtk-sharp, '=dev-dotnet/gecko-sharp-0.6', gmime, glade-sharp, gnome-sharp, and gconf-sharp with the mono USE flag on. my `emerge info`: Portage 2.0.51.22-r1 (default-linux/x86/2005.0, gcc-3.4.4, glibc-2.3.5-r0, 2.6.12-gentoo i686) ================================================================= System uname: 2.6.12-gentoo i686 AMD Athlon(tm) XP 1800+ Gentoo Base System version 1.6.12 dev-lang/python: 2.3.5, 2.4.1-r1 sys-apps/sandbox: 1.2.9 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.18 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=athlon-xp -Os -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control"CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-march=athlon-xp -Os -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ ftp://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://ftp.easynet.nl/mirror/gentoo/ ftp://ftp.easynet.nl/mirror/gentoo/ http://mirror.gentoo.no/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://ftp.belnet.be/gentoo-portage/" USE="x86 3dnow 3dnowex 3dnowext X X509 a52 aac aalib acpi acpi4linux alsa anvode apache2 audiofile avi bash-completion bitmap-fonts bonobo bzip2 bzlib c++ cairo cdda cddb cdparanoia cdr chroot cjk clisp codecs crypt css ctype curl curlwrappers custom-cflags daap dbm dbus dga directfb divx4linux dmx dpms dts dvd dvdread emboss emoticon encode enscript epiphany epson esd exif fame fbcon fdftk festival ffmpeg figlet finger firefox flac flash foomaticdb fortran freetts ftp gb gcj gd gdbm geoip gif gimp gimpprint ginac gkrellm glade glibc glitz glut gnome gnome-print gnuplot gnutls gpm graphviz gs gstreamer gtk gtk2 gtkhtml h323 hal howl html http httpd icq idn iksemel imagemagick imap imlib imlib2 inifile inkjar jabber java javascript jikes jpeg jpeg2k junit lcms libcaca libg++ libwww live lm_sensors lzo lzw lzw-tiff mad matrox mbrola mcal mikmod mime ming mjpeg mmx mmx2 mmxext mng mono motif mozcalendar mozilla moznocompose moznoirc moznomail mozp3p mozplaintext mp3 mpeg mpeg2 mpeg4 mplayer msn mysql ncurses network nls nptl nvidia octave offensive ogg oggvorbis openal opengl oss pam pdflib perl php plotutils png posix ppds python qhull quicktime rar readline real reiserfs rss rtc samba sblive scanner screenshot sdl sensord session sftp sftplogging shared sharedmem slang sockets sounds sox speex spell spl sqlite sse sse2 ssl stream stroke subp subtitles svg svga t1lib tcltk tcpd tetex tga theora tidy tiff truetype truetype-fonts type1 type1-fonts unicode usb utf8 uudeview v4l v4l2 vcd vidix vim vorbis win32codecs wmf wxwindows xanim xine xinerama xml xml2 xmlrpc xmms xosd xpm xprint xsl xv xvid xvmc yahoo zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
beagle 0.0.11.1 is not compatible with gmime 2.1.15
Builds fine against gmime 2.1.14 but not against 2.1.15.
(In reply to comment #157) > Builds fine against gmime 2.1.14 but not against 2.1.15. Correct if you replace 2.1.14 wth 2.1.14-r1 :-) It's running fine now, except that beagled keeps on crashing when some backends are allowed. it seems to be stable on Files an IMLog, but not on Mail and Launcher. I always crashes with the same error, being: mono-beagled: ./src/os.c:1751: sqliteOsEnterMutex: Assertion `!inMutex' failed. This is reproducible. Still testing the others. (I don't have evolution installed, nor have I used the eds USE flag)
Using the 0.0.11-r1 ebuild failed with the following error message, while 0.0.9 compiled cleanly. Compilation succeeded ExtendedAttribute.cs(45) error CS0117: `Beagle.Util.ExternalStringsHack' does not contain a definition for `XattrLib' ExtendedAttribute.cs(48) error CS0117: `Beagle.Util.ExternalStringsHack' does not contain a definition for `XattrLib' ExtendedAttribute.cs(51) error CS0117: `Beagle.Util.ExternalStringsHack' does not contain a definition for `XattrLib' ExtendedAttribute.cs(57) error CS0117: `Beagle.Util.ExternalStringsHack' does not contain a definition for `XattrLib' ExtendedAttribute.cs(60) error CS0117: `Beagle.Util.ExternalStringsHack' does not contain a definition for `XattrLib' ExtendedAttribute.cs(63) error CS0117: `Beagle.Util.ExternalStringsHack' does not contain a definition for `XattrLib' Compilation failed: 6 error(s), 0 warnings make[2]: *** [Util.dll] Error 1 make[2]: Leaving directory `/var/tmp/portage/beagle-0.0.11-r1/work/beagle-0.0.11/Util' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/beagle-0.0.11-r1/work/beagle-0.0.11' make: *** [all] Error 2 !!! ERROR: gnome-extra/beagle-0.0.11-r1 failed. !!! Function gnome2_src_compile, Line 41, Exitcode 2 !!! compile failure !!! If you need support, post the topmost build error, NOT this status message. ~ # emerge info Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.12-gentoo-iseult i686) ================================================================= System uname: 2.6.12-gentoo-iseult i686 AMD Athlon(tm) XP 2600+ Gentoo Base System version 1.6.12 Python: dev-lang/python-2.3.5 [2.3.5 (#1, Jun 23 2005, 19:45:04)] ccache version 2.3 [enabled] dev-lang/python: 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r1, 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/X11/app-default /etc/X11/gdm/Init /etc/X11/gdm/PostLogin /etc/X11/gdm/PostSession /etc/X11/gdm/PreSession /etc/X11/gdm/Sessions /etc/X11/gdm/modules /etc/X11/mwm /etc/X11/rstart /etc/X11/sysconfig/ /etc/X11/xdm/ /etc/bash_completion.d/ /etc/dbus-1/ /etc/gconf /etc/gimp/ /etc/gnome-vfs-2.0/modules/ /etc/init.d/ /etc/mono/ /etc/pam.d/ /etc/skel/ /etc/sound/events/ /etc/ssl/misc/ /etc/terminfo /etc/udev /etc/vim/ /etc/wget /usr/X11R6/lib/ /usr/lib/X11/ /usr/share/texmf/ /etc/env.d" CXXFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.math.bme.hu http://gentoo.osuosl.org/ ftp://mirrors1.netvisao.pt/gentoo/" LINGUAS="en fr it" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/bugzilla-portage" SYNC="rsync://rsync.us.gentoo.org/gentoo-portage" USE="x86 3dnow 3dnowex X Xaw3d acl acpi alsa avi bash-completion berkdb bitmap-fonts bonobo c++ cdr crypt cups curl dillo djvu doc dvd dvi eds emacs emboss encode esd evo f77 fam font-server foomaticdb fortran gcj gd gdbm gif gimpprint ginac gnome gpm gstreamer gtk gtk2 gtkhtml guile hal imagemagick imlib java jpeg libg++ libwww mad maildir mikmod mmx mono motif mozilla mozsvg mp3 mpeg ncurses network nfs nls nptl objc ogg oggvorbis opengl pam pda pdf pdflib perl png ppds python qhull quicktime readline samba sdl slang slp spell sqlite sse ssl svg svga t1lib tcltk tcpd tetex theora tiff truetype truetype-fonts type1-fonts unicode usb userlocales vim-with-x vorbis wmf xml xml2 xmms xv zlib video_cards_r100 linguas_en linguas_fr linguas_it userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS
suggestion: since configure for beagle shows these options for the --with-mozilla switch: --with-mozilla[=mozilla|firefox|thunderbird] Whether to use mozilla, firefox or thunderbird gtkmozembed (default: mozilla) we could get rid of the static mozilla dep changing the ebuild as follows: in the DEPEND= section: -www-client/mozilla" +!firefox? ( >=www-client/mozilla-1.7.3 ) +firefox? ( >=www-client/mozilla-firefox-1.0.2-r1 )" change the G2CONF line: -G2CONF="${G2CONF} `use_enable epiphany epiphany-extension` --with-mozilla=mozilla --disable-epiphany-extension-install `use_enable network`" +G2CONF="${G2CONF} `use_enable epiphany epiphany-extension` --disable-epiphany-extension-install `use_enable network`" +if use firefox; then + G2CONF="${G2CONF} --with-mozilla=firefox" +else + G2CONF="${G2CONF} --with-mozilla=mozilla" +fi it should work :) hth alessandro
oops, forgot to mention: -IUSE="doc eds epiphany network" +IUSE="doc eds epiphany network firefox"
Created attachment 62741 [details] beagle-0.0.11.1 with firefox support beagle-0.0.11.1 with firefox support
Bealge needs the mozilla browser even when I have firefox in? I have tryed with both with and wirhout the firefox useflag. [ebuild N ] dev-db/sqlite-2.8.16-r1 -doc +nls -tcltk 958 kB [ebuild N ] dev-dotnet/libgdiplus-1.1.8 +gif +jpeg +png +tiff 1,321 kB [ebuild N ] dev-lang/mono-1.1.8.1 +X -icu +nptl 14,978 kB [ebuild N ] dev-dotnet/gtk-sharp-1.0.8-r1 1,799 kB [ebuild N ] dev-dotnet/art-sharp-1.0.8-r1 0 kB [ebuild N ] dev-dotnet/gnome-sharp-1.0.8-r1 0 kB [ebuild N ] dev-dotnet/glade-sharp-1.0.8-r1 0 kB [ebuild N ] dev-dotnet/gconf-sharp-1.0.8-r1 0 kB [ebuild N ] app-text/wv-1.0.0-r1 -wmf +xml2 709 kB [ebuild N ] www-client/mozilla-1.7.8 -crypt -debug +gnome -java -ldap -mozdevelop +moznomail +moznoxft +mozsvg -mozxmlterm -postgres +ssl +xinerama +xprint 0 kB [ebuild N ] dev-dotnet/gecko-sharp-0.6 108 kB [ebuild N ] app-misc/beagle-0.0.11.1 -debug -doc -eds -epiphany +firefox +network 0 kB [1]
You need a Firefox-enabled gecko-sharp ebuild, see bug #92868.
Created attachment 63190 [details] beagle-0.0.12.ebuild Upgraded beagle to 0.0.12. Updated Mono dependancy to 1.1.8.2 and Gmime deps to 2.1.15.
Created attachment 63206 [details] beagle-0.0.12 by Dave + firefox patch beagle-0.0.12 by Dave with the firefox patch updated for the new ebuild
spoke to latexer and Gnome herd. Taking ownership of this one with dsd. We're going to wait on mono 1.1.9's release before adding this to the tree. The ebuild from the Gentopia overlay will most likely be the one pulled in.
Just out of curiosity, any idea on timeline for that release? Also, how is this working on AMD64... I myself have been reluctant to test, simply because it's enough of a hassle to do an overlay for just architecture... overlaying something not in the tree yet seemed like more hassle than it was worth, especially with all of beagle's dependencies. That said, once it goes into the tree, I'll definitely be testing, assuming that at least the dependencies are at least in ~amd64. Good work though... I'm really excited to get to try this out soon.
Comment on attachment 63190 [details] beagle-0.0.12.ebuild Heh.. Alessandro, you beat me too it.
Slow down there... ;) There are two issues that need solving. One which will be solved by mono 1.1.9 (with an additional beagle patch) - crashes while indexing 'odd' filenames. Mono 1.1.9 will then become a requirement by the ebuild. The other is the excessive memory usage when querying. Last time I checked, beagled sat at about 30mb memory usage continually (which is fine), until you do a query. A few queries later, you are at 150mb and still growing, making the rest of your system quite unusable. There is ongoing work to try and combat this, but I'd like to see it solved before beagle goes into portage. If people want to play around and see how much the situation has improved as of 0.0.12 (it will certainly be a lot better) then please post your reports here. Also, Doug, I'd like to go over the ebuild with you (I haven't looked at it yet, but I have a few ideas of my own).
The inotify patch included into 2.6.13 (since -rc3) features a new API based on syscalls instead of /dev/inotify (hopefully this will be the last inotify change for a while ;)). Changes are in Beagle CVS, patch is available here: http://mail.gnome.org/archives/dashboard-hackers/2005-July/msg00026.html The new inotify glue-code is no longer compatible with the old (< 0.24) inotify API. So starting with Beagle 0.0.13, you either need kernel >=2.6.13-rc3 or use version 0.24 of the inotify patch. How do you want to deal with this? I'd suggest waiting at least (depending on the other issues left) until beagle 0.0.13 and then having beagle depend on virtual/linux-sources-2.6.13 (or the appropriate version of gentoo-sources if you intend to include inotify 0.24).
(In reply to comment #171) > How do you want to deal with this? > I'd suggest waiting at least (depending on the other issues left) until beagle > 0.0.13 and then having beagle depend on virtual/linux-sources-2.6.13 (or the > appropriate version of gentoo-sources if you intend to include inotify 0.24). Beagle does not require inotify (but does work a lot nicer if you have it) Those running on older kernels will still be able to use beagle
For all that are interested in Beagle. Daniel (dsd) and I are very aware of all changes happening to Beagle. Daniel happens to be Beagle upstream and both of are are active on the mailing list as well as on their IRC channel. We speak with the developers on a daily basis, so status updates to this bug for our information is old news. With regard to the ebuild, the Beagle IRC channel has had several users come in complaining about Beagle failing to compile or not work, turns out they were using the ebuild from this bug so I'm going to say, please use the Gentopia https://dev.cardoe.com/gentopia/overlay/app-misc/beagle/ ebuilds and not the one here since those users switched and all was well. I maintain that ebuild actively and it will be updated for each release. Daniel also has write access to that ebuild so if anything needs to be changed we're both available to fix that one. Also, that ebuild is the basis for the official Gentoo ebuild.
Hi, I try since 1 week to access https://dev.cardoe.com/gentopia/overlay/app-misc/beagle/ I get no answer from the server....
https://dev.cardoe.com/gentopia/overlay/app-misc/beagle/ This link gives me no response as well.
According to one of the Gentopia developers, they pretty much closed that site down and it will be operating out of break my gentoo (http://www.breakmygentoo.org/).
http://www.cardoe.com/archives/2005/08/06/gentopia-strikes-back/#comments It appears Gentopia is quite separate from BMG.
Ooops.. :-). Well, the blog posting was what I was refering *misquoting* from, looks like it will be at http://www.gentooexperimental.org/.
Soo... where are the ebuilds at? I got beagle-0.0.9 to compile on amd64 using mono-1.1.2.
* beagle-0.0.12-r1, mono-1.1.8.2 on x86 http://www.cardoe.com/archives/2005/08/10/gentopia-tomorrow/
Beagle 0.0.12-r1 has hit Gentopia. You'll notice some changes to it. However, I'm running modular X and due to a bug over there @ freedesktop.org, Beagle will not compile with modular X currently.
The gentoopia ebuild seems to not have support for the new vanilla kernel's inotify support. Perhaps a patch could be added to the ebuild.
Beagle 0.0.12 is currently what Gentopia carries which contains the 0.23-x series of the inotify interface code. The 0.23-x series of the inotify interface is not present in any vanilla kernel. However, gentoo-sources and suspend2-sources, along with other Gentoo kernel contain the 0.23-x series interface. The 0.24-x series interface, which is present in RC of the next vanilla kernel, is currently only supported in Beagle CVS, which Gentopia does not track at this time. The 2.6.13 kernel, when released to stable, will contain the 0.24-x series interface. At that time, Beagle 0.0.13, with 0.24-x interface code will be released. As such, Gentopia sticks to the same Gentoo stance of "We do not support kernel RCs". And as such, no patch will be intergrated since it would break compatiblity with stable series kernels.
The ebuild provided as attachment 63206 [details] requires one extra step to use Firefox without also pulling in Mozilla. The ebuild for gecko-sharp-0.6 must be edited to remove the Mozilla Suite dependency. I'm not sure exactly what it requires, but it works on my system so I assume firefox and gecko-sdk provide a suitable substitute.
Here's what we need to do before adding beagle 0.1.0 to portage: - Patch wv1 with the fix from beagle mailing list - Get gtk-sharp-2 removed from package.mask - Add beagle use-flag to gnumeric (not essential right now) To simplify things, the first ebuild will disable evolution-sharp support, so address book wont be indexed. We'll add evolution-sharp to portage at a later date.
Daniel: Just an FYI, I changed the package.mask to only mask 2.5.x stuff right now. 2.3.x and friends are out of package.mask. The reason only the 2.3.x stuff is out is because upstream has been adamant about folks not packaging 2.5.x stuff because of assembly version changes and API additions which may be a problems since most 'major' distros don't ship gtk+-2.6 yet (or are just starting too).
Created attachment 68683 [details] Updated Beagle 0.1.0 ebuild Updated for 0.1.0. Used Gentopia's ebuild 0.0.12-r1 as base. Unfortunately, Gentopia's site is down and I don't know how to submit this ebuild to them. Changes: - Removed eds as beagle requires version of eds which is not yet in the tree. - Removed gnumeric USE flag - Updated deps Ebuild still needs some polishing.. but should work.
(In reply to comment #187) This ebuild depends on gmime-2.1.16 with the mono use flag set, but that version does not have that flag...
hi! i've tried the version beagle-0.1.0 and i've failed it: error CS0006: Cannot find assembly `BeagleWebServicesFrontEnd.dll' Log: Compilation failed: 2 error(s), 0 warnings make[2]: *** [IndexHelper.exe] Erreur 1 make[2]: *** Attente des t
hi! i've tried the version beagle-0.1.0 and i've failed it: error CS0006: Cannot find assembly `BeagleWebServicesFrontEnd.dll' Log: Compilation failed: 2 error(s), 0 warnings make[2]: *** [IndexHelper.exe] Erreur 1 make[2]: *** Attente des tâches non terminées.... ./WebServices/ExternalAccessFilter.cs(86,13): warning CS0219: The variable `fa' is assigned but its value is never used ./WebServices/WebBackEnd.cs(741,9): warning CS0219: The variable `j' is assigned but its value is ne ver used Compilation succeeded - 2 warning(s) make[2]: Leaving directory `/var/tmp/portage/beagle-0.1.0/work/beagle-0.1.0/beagled' make[1]: *** [all-recursive] Erreur 1 make[1]: Leaving directory `/var/tmp/portage/beagle-0.1.0/work/beagle-0.1.0' make: *** [all] Erreur 2 !!! ERROR: app-misc/beagle-0.1.0 failed. !!! Function gnome2_src_compile, Line 48, Exitcode 2 any suggestions please?
What version of mono do you have installed? (In reply to comment #189) > hi! > i've tried the version beagle-0.1.0 and i've failed it: > > error CS0006: Cannot find assembly `BeagleWebServicesFrontEnd.dll' > Log: > > Compilation failed: 2 error(s), 0 warnings > make[2]: *** [IndexHelper.exe] Erreur 1 > make[2]: *** Attente des t
What version of mono do you have installed? (In reply to comment #189) > hi! > i've tried the version beagle-0.1.0 and i've failed it: > > error CS0006: Cannot find assembly `BeagleWebServicesFrontEnd.dll' > Log: > > Compilation failed: 2 error(s), 0 warnings > make[2]: *** [IndexHelper.exe] Erreur 1 > make[2]: *** Attente des tâches non terminées.... > ./WebServices/ExternalAccessFilter.cs(86,13): warning CS0219: The variable `fa' > is assigned but its > value is never used > ./WebServices/WebBackEnd.cs(741,9): warning CS0219: The variable `j' is assigned > but its value is ne > ver used > Compilation succeeded - 2 warning(s) > make[2]: Leaving directory `/var/tmp/portage/beagle-0.1.0/work/beagle-0.1.0/beagled' > make[1]: *** [all-recursive] Erreur 1 > make[1]: Leaving directory `/var/tmp/portage/beagle-0.1.0/work/beagle-0.1.0' > make: *** [all] Erreur 2 > > !!! ERROR: app-misc/beagle-0.1.0 failed. > !!! Function gnome2_src_compile, Line 48, Exitcode 2 > > any suggestions please? > >
(In reply to comment #190) > What version of mono do you have installed? dev-lang/mono-1.1.9
(In reply to comment #189) The same with me (mono version 1.1.9). It seems to be an error with parallel builds, to solve it you just need to temporarily comment out any "-j" you have in MAKEOPTS in /etc/make.conf and rebuild beagle. - gianluca > hi! > i've tried the version beagle-0.1.0 and i've failed it: > > error CS0006: Cannot find assembly `BeagleWebServicesFrontEnd.dll' > [...] > any suggestions please? >
I'm trying to test this ebuild but I've run across a few problems, two of which I saw previous comments about: 1) I'm on an Athlon64 and it doesn't have the ~amd64 keyword. Easy workaround, I edited the file. 2) gmime does not take a mono use flag anymore. Easy fix, commented those lines :) 3) I'm using a binary build of Firefox and the configure script dies when it looks for a mozilla install: checking which mozilla to use... configure: error: unable to find gtkmozembed; this can be found in mozilla/firefox/thunderbird development packages !!! Please attach the config.log to your bug report: !!! /var/tmp/portage/beagle-0.1.0-r1/work/beagle-0.1.0/config.log !!! ERROR: app-misc/beagle-0.1.0-r1 failed. !!! Function econf, Line 496, Exitcode 0 !!! econf failed !!! If you need support, post the topmost build error, NOT this status message. I tried commenting out the part of the ebuild that checks for mozilla and/or firefox but it didn't seem to help. There was some discussion earlier about use of the mozilla/firefox use flags. Unless I misunderstood it was in there originally but was removed because people didn't think it was needed..? This is where that flag would come in handy :) I've got several packages that won't build with mozilla/firefox support and that's usually what the flag is for. Yelp is a good example. If anyone knows how I can edit the ebuild to remove the mozilla check I'd love to give feedback on the amd64 platform.
Created attachment 69812 [details] beagle-0.1.1.ebuild Changes: - added chm and gnumeric use flags - added ~amd64 keyword - fixed mozilla/firefox dependencies - cleaned up ebuild
(In reply to comment #193) > I'm trying to test this ebuild but I've run across a few problems, two of which > I saw previous comments about: > > 1) I'm on an Athlon64 and it doesn't have the ~amd64 keyword. Easy workaround, > I edited the file. > 2) gmime does not take a mono use flag anymore. Easy fix, commented those lines :) > 3) I'm using a binary build of Firefox and the configure script dies when it > looks for a mozilla install: > > checking which mozilla to use... configure: error: unable to find gtkmozembed; > this can be found in mozilla/firefox/thunderbird development packages > > !!! Please attach the config.log to your bug report: > !!! /var/tmp/portage/beagle-0.1.0-r1/work/beagle-0.1.0/config.log > > !!! ERROR: app-misc/beagle-0.1.0-r1 failed. > !!! Function econf, Line 496, Exitcode 0 > !!! econf failed > !!! If you need support, post the topmost build error, NOT this status message. > > I tried commenting out the part of the ebuild that checks for mozilla and/or > firefox but it didn't seem to help. There was some discussion earlier about use > of the mozilla/firefox use flags. Unless I misunderstood it was in there > originally but was removed because people didn't think it was needed..? This is > where that flag would come in handy :) I've got several packages that won't > build with mozilla/firefox support and that's usually what the flag is for. > Yelp is a good example. > > If anyone knows how I can edit the ebuild to remove the mozilla check I'd love > to give feedback on the amd64 platform. I've just submitted beagle-0.1.1.ebuild to bugzilla which adds the ~amd64 keywording. The GMIME issue is solved according to bug# 106071. There's also some changes in the ebuild on how it detects firefox/mozilla. Give it a try and let us know if your still having an issue.
I went ahead and installed a cvs build of Firefox on my desktop but I can try the new build out on my laptop (which runs the nightly binary builds) tomorrow. For now I have more build problems. After I get past the mozilla config check it failes with the same thing that happened in comment 153. It is expecting me to have gmime-sharp installed, a package which doesn't seem to exist. Here's the error: checking for BEAGLE_UI... configure: error: Package requirements (gtk-sharp-2.0 glade-sharp-2.0 gecko-sharp-2.0 gnome-sharp-2.0 gconf-sharp-2.0 gmime-sharp >= 2 .1.16) were not met. Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively you may set the BEAGLE_UI_CFLAGS and BEAGLE_UI_LIBS environment va riables to avoid the need to call pkg-config. See the pkg-config man page for more details. Here's the -sharp packages I have installed: [ I] dev-dotnet/art-sharp (2.3.91): art component of gtk-sharp [ I] dev-dotnet/gconf-sharp (2.3.91): gconf component of gtk-sharp [ I] dev-dotnet/gecko-sharp (0.11): A Gtk# Mozilla binding [ I] dev-dotnet/glade-sharp (2.3.91): glade component of gtk-sharp [ I] dev-dotnet/gnome-sharp (2.3.91): gnome component of gtk-sharp [ I] dev-dotnet/gnomevfs-sharp (2.3.91): gnomevfs component of gtk-sharp [ I] dev-dotnet/gtk-sharp (2.3.91): Gtk# is a C# language binding for the GTK2 toolkit and GNOME libraries
I've just tried to install the beagle-0.1.1 ebuild on my x86 laptop and it still has some problems. It still complains about gtkmozembed when I try to compile it against a binary build of Firefox. It seems that the new ebuild is no better than the last in this respect. The problem seems to be in Beagle's configure script rather than the ebuiild. Is there any kind of option that can be passed to it in order to avoid the firefox check entirely? If so then that should be done if the firefox use flag is not set. I'm also still having my problem 2 from comment 193. It is checking for the mono use flag but that version of gmime doesn't take that flag. Since 2.1.16 is the minimum verson required by this ebuild that check can just be removed.
Created attachment 70062 [details] app-misc/beagle-0.1.1.ebuild Here's an ebuild based slightly on the gentopia one which will go into portage pending any feedback. As for the mozilla stuff, beagle requires a development library only provided by the from-source mozilla/firefox/thunderbird packages, the -bin packages do not provide the libraries that beagle needs. Also, beagle depends on gecko-sharp which depends on mozilla (i.e. not ffox/tbird) so for now the beagle ebuild will do the same. gecko-sharp may be modified to support mozilla OR firefox OR thunderbird sometime in the near future when some issues have been ironed out, in which case we can modify beagle's dependencies too.
Created attachment 70063 [details, diff] files/beagle-0.1.1-null-task-source.patch A crash fix
Created attachment 70064 [details, diff] files/beagle-0.1.1-uri-serialization.patch A filename handling fix
looks like the KopeteQueryable.cs part of the patch (null-task-source.patch) is already in the source, so the patch fails..? I removed this section from the patch file and the ebuild then worked with the 2 patches.
It is not, I wrote that patch after 0.1.1 was released. After a clean unpack of 0.1.1, : # grep Source beagle-0.1.1/beagled/KopeteQueryable/KopeteQueryable.cs returns nothing. Are you sure you are working on a clean 0.1.1? Can anyone else confirm or deny that the patch fails to apply? It works fine here.
worked just fine here with all the patches being applied
hmm, maybe I did something odd then. I checked it before posting by doing rm-rf /var/tmp/portage/beagle-0.1.1/ and then re-emerging - so it should have unpacked a clean src tree.. Oh well, it was very late, anything could have happened. It's working nicely at any rate :)
Cleaning out old files and rebuilding based on the latest ebuild+patches works here with no problems as well. FWIW, this is on AMD64.
The patches apply cleanly but I still can't emerge the new ebuild for the same reason as before. It seems that I *can't* use the mono flag on gmime: $ USE="mono" emerge -pv gmime These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] dev-libs/gmime-2.1.16 -debug -doc +ipv6 (-mono) 0 kB And then the config fails with: checking for BEAGLE_UI... configure: error: Package requirements (gtk-sharp-2.0 glade-sharp-2.0 gecko-sharp-2.0 gnome-sharp-2.0 gconf-sharp-2.0 gmime-sharp >= 2.1.16) were not met. That failure is probably because of my gmime problem I guess. I'm on amd64, so why can't I use the mono flag won't work.
Because that use flag is masked on amd64 # 2005/01/12 - Benjamin Schindler <config@gentoo.org> # Optional mono support will never work until we have a stable mono compiler # Update: 2005/05/15 - Tom Martin <slarti@gentoo.org> # Will work with mono 1.1.6, waiting on that to be stabilised. mono
Wasn't that mask removed? I'm on AMD64 and everything is running properly. emerge -pv gmime These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] dev-libs/gmime-2.1.16 -debug -doc +ipv6 +mono 0 kB
Probably depends on your portage profile, however it is definately there for the base amd64 stuff
I'm using the 2005.1 amd64 profile: $ ls -l /etc/make.profile lrwxrwxrwx 1 root root 50 Sep 7 19:27 /etc/make.profile -> ../usr/portage/profiles/default-linux/amd64/2005.1 And use.mask definitely shows mono in there with the comment shown in comment 207. Since that version is long-since out, why not remove that from the profile? Jose daLuz: Are you using the same profile and did you have to modify your use.mask file at all to make gmime merge with the mono flag?
Interesting: ls -l /etc/make.profile lrwxrwxrwx 1 root root 48 Aug 11 07:32 /etc/make.profile -> /usr/portage/profiles/default-linux/amd64/2005.1 ls -l /etc/make.profile/use.mask -rw-r--r-- 1 root root 239 Jun 4 17:20 /etc/make.profile/use.mask cat /etc/make.profile/use.mask # $Header: /var/cvsroot/gentoo-x86/profiles/default-linux/amd64/2005.1/use.mask,v 1.1 2005/06/04 21:20:09 eradicator Exp $ # Jeremy Huddleston <eradicator@gentoo.org> # multilib is forced on when we have ${MULTILIB_ABIS} defined multilib I did not modify use.mask -- I didn't even know about it until today.
Alright, I've commented the mono line from use.mask. All 3 of the packages in world that wanted that flag got it with no trouble. However the build itelf fails b/c Beagle doesn't like my CVS mozilla build. Can we get the mono flag out of use.mask for the amd64 platform? I grabbed the Beagle code from CVS but I can't find any way to disable the Firefox extension. On Beagle's wiki Firefox is listed as an optional prerequisite. There really needs to be a way to remove its dependency from the ebuild. I don't think it's a valid solution to require a source build of Firefox, especially when all it does is build an extension that can be retrieved online anyway. I've read the INSTALL file and all of the documentation I can find and there doesn't seem to be a specific way to completely disable Mozilla support. Has anyone sucessfully built Beagle w/o Mozilla/Firefox support? How about with a binary build installed instead of a source build? This may need to be filed as a Beagle bug if no config option exists. Oh - and the new ebuild needs the ~amd64 keyword added to it.
(In reply to comment #212) > Can we get the mono flag > out of use.mask for the amd64 platform? Read the comment in the file: # Will work with mono 1.1.6, waiting on that to be stabilised. Mono 1.1.8 will be the first 1.1 marked stable soon, but you'll have to be patient for our 1 man mono team to iron out all the issues. > I grabbed the Beagle code from CVS but I can't find any way to disable the > Firefox extension. On Beagle's wiki Firefox is listed as an optional > prerequisite. There really needs to be a way to remove its dependency from the > ebuild. I don't think it's a valid solution to require a source build of > Firefox, especially when all it does is build an extension that can be retrieved > online anyway. Beagles search tool, Best, uses gecko (a mozilla component) to render the search results. This is the primary reason why moz/ffox/tbird is a requirement. There is no way to disable it, beagle would be pretty useless that way. > Oh - and the new ebuild needs the ~amd64 keyword added to it. The amd64 arch team will have to take care of that as I can not test on amd64. Once the ebuild is in portage, feel free to file a bug with them.
...and of course, the amd64 team will probably reject that, because the ebuild will fail for all amd64 users as they cannot build gmime with mono bindings at this point in time.
(In reply to comment #214) > ...and of course, the amd64 team will probably reject that, because the ebuild > will fail for all amd64 users as they cannot build gmime with mono bindings at > this point in time. I'd like to disagree here. I build gmime with mono just fine. And mono is past 1.1.6 now, i'm on 1.1.9.1. None of the builds > 1.1.6 are using kw amd64 yet (only ~amd64), but I don't think this will still be the case when the next portage profile becomes available. (In reply to comment #213) > Beagles search tool, Best, uses gecko (a mozilla component) to render the > search. Err... Firefox is listed on the Optional prerequisites page: http://beaglewiki.org/Optional_prerequisites. Although gecko-sharp *is* listed as a requirement I maintain that Firefox should not be. The errors I'm getting at compile tile are about undefined methods and stuff not returning types, all involving files in my Firefox install directory. It might be necessary to file a bug for beagle not compiling against Firefox CVS. Meantime, does anyone know how to tell beagle not to build the Mozilla extension? I'd like to try that to see if it builds but I haen't been able to figure out how. When I run autogen.sh in the CVS checkout it ends with this config summary: Target OS: linux Extended Attributes: libc Prefix: /usr/local GNOME Prefix: /usr KDE Prefix: /usr/kde/3.4 Evolution-Sharp? no (missing dependencies) gsf-sharp? no Epiphany Extension? no (Epiphany not installed) Mozilla Extension? yes wv1? yes galago-sharp? no libchm? no Local SqliteClient? yes Sqlite version: 2.x Enable WebServices no Enable libbeagle yes I would like the make the "Mozilla Extension?" line say "no".
(In reply to comment #215) > I'd like to disagree here. I build gmime with mono just fine. I'm not sure why that is, because mono is use.mask'd in the base amd64 profile. Maybe a bug in portage. > And mono is past > 1.1.6 now, i'm on 1.1.9.1. None of the builds > 1.1.6 are using kw amd64 yet > (only ~amd64), but I don't think this will still be the case when the next > portage profile becomes available. The comment in use.mask implies that it won't be removed until >1.1.6 is *marked stable*, regardless of the latest version available in the testing tree. And stabilisation is done after bugs are fixed and the package has been tested, rather than on profile upgrade. > Err... Firefox is listed on the Optional prerequisites page: > http://beaglewiki.org/Optional_prerequisites. Although gecko-sharp *is* listed > as a requirement I maintain that Firefox should not be. gecko-sharp is a simple C# interface to libgtkmozembed. gtkmozembed is provided by from-source mozilla builds. gecko-sharp therefore depends on mozilla, it will not work without it. Also, firefox is not a requirement at all. Although firefox does provide gtkmozembed, firefox is a web browser, and there are inconsistencies between the gtkmozembed's provided by firefox and mozilla itself. As mentioned above, the beagle ebuild will depend on www-client/mozilla to be consistent with the gecko-sharp ebuild. > The errors I'm getting at compile tile are about undefined methods and stuff not > returning types, all involving files in my Firefox install directory. It might > be necessary to file a bug for beagle not compiling against Firefox CVS. Yes, beagle's glue code will not compile against mozilla cvs releases. > Meantime, does anyone know how to tell beagle not to build the Mozilla > extension? I'd like to try that to see if it builds but I haen't been able to > figure out how. It is unconditionally built. You can probably remove mozilla-extension from SUBDIRS in the main Makefile.am and then re-autogen to stop it being built.
on AMD64, compiling beagle-0.0.12-r1 crashes with ./TileBlog.cs(47,18): error CS0021: Cannot apply indexing with [] to an expression of type `Beagle.Hit' ./TileBlog.cs(54,8): error CS0021: Cannot apply indexing with [] to an expression of type `Beagle.Hit' ./TileBlog.cs(55,30): error CS0021: Cannot apply indexing with [] to an expression of type `Beagle.Hit' ./TileBlog.cs(55,8): error CS1502: The best overloaded method match for `Beagle.Tile.Template.this[string]' has some invalid arguments ./TileBlog.cs(55,8): error CS1503: Argument 2: Cannot convert from `object' to `string' ./TileBlog.cs(55,8): error CS1501: No overload for method `this' takes `1' arguments ./TileBlog.cs(62,21): error CS0021: Cannot apply indexing with [] to an expression of type `Beagle.Hit' ./TileBlog.cs(64,63): error CS0021: Cannot apply indexing with [] to an expression of type `Beagle.Hit' ./TileImLog.cs(57,25): error CS0021: Cannot apply indexing with [] to an expression of type `Beagle.Hit' Compilation failed: 9 error(s), 0 warnings make[2]: *** [Tiles.dll] Error 1 make[2]: Leaving directory `/var/tmp/portage/beagle-0.0.12-r1/work/beagle-0.0.12/Tiles' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/beagle-0.0.12-r1/work/beagle-0.0.12'make: *** [all] Error 2 !!! ERROR: app-misc/beagle-0.0.12-r1 failed. !!! Function gnome2_src_compile, Line 48, Exitcode 2 !!! compile failure !!! If you need support, post the topmost build error, NOT this status message.
Re: comment #217 Given beagle is at 0.1.1 and given 0.0.12 doesn't even *work* with a 2.6.13 kernel - is there really much point in pasting long compile errors in an already long bug? That's like noting 2.2 kernels don't work on AMD64 - not terribly useful.
Beagle is now available in portage. The ebuild is slightly different from the one posted here, and the uri-serialization patch was updated, so you should upgrade to the version available in portage if you tested the version posted here. Thanks everyone for testing and feedback. Installation instructions can be found here: http://www.beaglewiki.org/Gentoo_Installation
Forgot to mention, the ebuild in portage lacks support for gsf (powerpoint presentation indexing), evolution (email indexing), and galago (tighter IM integration) as the required dependencies are not in portage. Bug 110323 is a tracker bug for getting these packages into the tree.
Created attachment 71527 [details] modified version of beagle with firefox support instead of mozilla I didn't want to install the whole mozilla suite, so I tried to modify a bit the beagle ebuilt and also the gecko-sharp ebuild. This is the first time I look an ebuild, may be there are mistakes, but till now everything works fine on my pc. And this is also the first time I install beagle so it really means it function :-) bye Nic
