Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#2789 - Beagle...
Attached to Project:
Arch Linux
Opened by Eugenia Loli-Queru (Eugenia) - Thursday, 02 June 2005, 23:40 GMT
Last edited by arjan timmerman (blaasvis) - Saturday, 01 October 2005, 14:51 GMT
Opened by Eugenia Loli-Queru (Eugenia) - Thursday, 02 June 2005, 23:40 GMT
Last edited by arjan timmerman (blaasvis) - Saturday, 01 October 2005, 14:51 GMT
|
DetailsI would like to request Beagle to be included in the repos. Currently, it's way too much work to get a third party beagle package and compile your own kernel too with inotify support. It would nice to have these by default in the kernel and all the deps in the repos. Beagle is the next generation coo-thing, and it is a must IMHO, especially now that MacOSX ships with Spotlight.
Also, adding f-spot, sportstracker, polarviewer, bless and muine would be a great way to enrich the mono support in the repos too. These are well-maintained apps, i don't expect too many support problems with them. |
This task depends upon
Closed by arjan timmerman (blaasvis)
Wednesday, 21 December 2005, 15:24 GMT
Reason for closing: Implemented
Additional comments about closing: beagle is in testing now.
Wednesday, 21 December 2005, 15:24 GMT
Reason for closing: Implemented
Additional comments about closing: beagle is in testing now.
About the other programs: we'll include them when we have time and see need for them. In the meanwhile: http://aur.archlinux.org
1) fam using inotify? Haven't heard about that one, fam seems to take advantage only of dnotify/polling. On the other hand, gamin takes full advantage of inotify and is whatsoever more friendly and mature (as of philosophy) solution, although it isn't perfect yet.
2) Rumours say that inotify is going to get merged into 2.6.13 (read: pretty soon), everyone's already sick of dnotify. But rumours are rumours, can't tell for sure ;-)
3) I'm a KDE user, using fam/gamin only for the purpose of refreshing content of konqueror. I'm currently using gamin built from cvs (ca. two bug fixes since official 0.1.0 release) and kernel patched with rml's inotify 0.23 and things work more or less flawlessly. I had problems with inotify patch included in mm, though (konqueror didn't always show proper content).
4) Concluding, I guess Arch should slowly move towards gamin and inotify, but some major testing needs to be done first. fam is a pretty buggy solution and currently gamin+inotify does a lot better work for me (fam goes crazy occasionally and eats all the cpu time), although I can't judge how it would behave in nautilus (I guess even better, as it's created by gnome circle). And beagle shouldn't have problems whatsoever, with its 'direct' access to inotify, I guess. So, I propose either to patch incoming 2.6.12 with rml's inotify 0.23 or to wait for it getting mainline, while preparing to dump fam for gamin.
begin, beagle builders. :)