You are not logged in.
i compiled glib and gtk with ubuntu patches, and installed indicator-appmenu successfully, but appmenu did not work correctly.
Offline
city-busz can you add to your repo the stable version of indicator-cpufreq? on AUR you can find only the -bzr version..
Offline
i compiled glib and gtk with ubuntu patches, and installed indicator-appmenu successfully, but appmenu did not work correctly.
Did you remember to add export UBUNTU_MENUPROXY="libappmenu.so" to your /etc/profile?
Offline
Could you also add indicator-keylock to the repository? https://launchpad.net/indicator-keylock
Edit: I've prepared a PKGBUILD. It builds & installs fine, but I can't get it to work. Trying to invoke indicator-keylock from the terminal results in this:
$ indicator-keylock
(indicator-keylock:32283): GLib-GObject-WARNING **: gsignal.c:2275: signal `child-added' is invalid for instance `0x9dd80d8'
(indicator-keylock:32283): GLib-GObject-WARNING **: gsignal.c:2275: signal `child-removed' is invalid for instance `0x9dd80d8'
Here's the PKGBUILD:
pkgname=indicator-keylock
pkgver=1.1.0
pkgrel=1
pkgdesc="Indicator for lock keys"
arch=('i686' 'x86_64')
url="https://launchpad.net/indicator-keylock"
license=('GPL')
groups=('ayatana')
depends=('libindicator>=0.3.0' 'libdbusmenu>=0.1.1' 'ido>=0.1.10' 'dconf>=0.5.1')
makedepends=('intltool')
options=(!libtool)
install=$pkgname.install
source=(http://launchpad.net/$pkgname/trunk/$pkgver/+download/${pkgname}_${pkgver}.orig.tar.gz)
md5sums=('f847f348e0af4d1400a6136531103474')
build() {
cd "$srcdir/$pkgname-$pkgver"
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libexecdir=/usr/lib
make
}
package() {
cd "$srcdir/$pkgname-$pkgver"
make DESTDIR="$pkgdir/" install
}
... and install file:
post_install() {
glib-compile-schemas usr/share/glib-2.0/schemas
}
post_upgrade() {
post_install $1
}
post_remove() {
post_install $1
}
Last edited by dcc24 (2011-02-13 21:44:45)
It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)
Offline
@City-busz: Sometimes, during pacman -Syu, I get 403 forbidden errors from your repo. Any idea why?
It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)
Offline
I've packaged another indicator app: Ejecter. It's working perfectly. This is especially useful since indicator-usb doesn't work and this app is not limited to USB drives, it supports CD/DVD etc.
App page: https://launchpad.net/ejecter
Description & screenshots: http://www.omgubuntu.co.uk/2011/01/ejec … t-support/
AUR package: http://aur.archlinux.org/packages.php?ID=46497
I've made it part of the 'ayatana' group. @City-busz, could you add this to your repo?
--------------------
Yet another indicator app: Lookit. It's a pretty cool screenshot tool and it works perfectly.
App page: https://github.com/zachtib/lookit
Description & screenshots: http://www.omgubuntu.co.uk/2010/08/look … hits-beta/
AUR package: http://aur.archlinux.org/packages.php?ID=46500
--------------------
Two more indicator apps! Pastie and Diodon. Both are working perfectly fine.
Description and screenshots: http://www.omgubuntu.co.uk/2011/01/the- … r-applets/
AUR pages
Pastie: http://aur.archlinux.org/packages.php?ID=43373
Diodon: http://aur.archlinux.org/packages.php?ID=46510
Last edited by dcc24 (2011-02-14 19:30:42)
It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)
Offline
Did you remember to add export UBUNTU_MENUPROXY="libappmenu.so" to your /etc/profile?
I tried but still the same. and error message from ~/.xsession-errors, i really don't know why.
(nautilus:16409): Gtk-WARNING **: Failed to load type module: (null)
`menu_proxy_module_load': nautilus: undefined symbol: menu_proxy_module_load
BTW: i am using gtk 2.24.0 and glib 2.28.0. And gtk 2.22.1 have the same problem. All indicator packages are bzr version.
Offline
@jarryson
Do you have appmenu-gtk from AUR installed?
Offline
anyone interested in packaging this one?
http://code.google.com/p/feedindicator/
You asked for it, you got it I've tested it and it works perfectly!
http://aur.archlinux.org/packages.php?ID=46604
On a side note, the developer's install script was torture to my eyes! The PKGBUILD is fine though
Edit: I've also adopted indicator-workspaces. It needed a complete rewrite and the PKGBUILD is less than perfect due to lousy installation script.
http://aur.archlinux.org/packages.php?ID=43375 (It works with a small problem, see the first AUR comment).
Anyway, I have now packaged 6 indicator apps and I'm willing to package others. Just post a request here and I'll do my best
Last edited by dcc24 (2011-02-17 22:51:43)
It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)
Offline
thank you!
anyway, can I ask how many of you
1) are using packages from ballo (or ballo-testing) repo?
2) are using the -bzr packages on AUR?
I'm using the first ones because sadly many bzr packages doesn't build on my system.. do any of you guys have the same problem?
Offline
Currently I'm using the ballo repo as well, but I'm in the process of building a new repo myself. I have lots of self-made Ayatana packages and City-busz seems to be MIA. Also his repo includes non-Ayatana packages as well and I'd like to create a pure Ayatana repo.
I'll post a link to it here when I'm done.
It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)
Offline
I've been working on creating a pure Ayatana repo for the past 8 hours now and I've noticed a few things:
- Almost all Ayatana packages on the ballo repo AND AUR are outdated and broken. Bumping $pkgver is not enough for most packages.
- Latest versions of libdbusmenu, libindicate etc. required A LOT of googling, patching and sed magic.
- As you might know, GObject Introspection is very, very broken and it's causing lots of issues for a lot of PKGBUILDs.
On the other hand, I'm almost done so I'll be creating a repo soon
It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)
Offline
New Pure Ayatana Repository!
After more than 12 hours of work, my repo is ready. Almost all packages are much more up to date than both AUR and ballo repos. You'll notice 2-3 packages are missing. This is due to library version mismatches (particularly libnotify, libdbusmenu and vala). I had to choose the lib versions that would allow me to compile the highest number of packages.
The repo is i686 only as I don't have an x86_64 build box (help is welcome). To use the repo, add the following in /etc/pacman.conf before any other repos:
[ayatana]
Server = http://repo.ayatana.info/
You can use the 'ayatana' group to install most indicators. I didn't have a chance to fully test this, so I'd appreciate it if you report back any issues. Enjoy
Edit:
Project homepage: http://ayatana.info/
Sources: http://sources.ayatana.info/
Last edited by dcc24 (2011-02-23 13:20:31)
It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)
Offline
thanks for your repo, i can't wait for plasma-message-indicator ^o^,
plasma-message-indicator's latest version is now in the repo! Enjoy
Also, if anyone wants a particular ayatana-related package to be included in the repo, just drop a note here.
Last edited by dcc24 (2011-02-20 12:35:42)
It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)
Offline
hellnest wrote:thanks for your repo, i can't wait for plasma-message-indicator ^o^,
plasma-message-indicator's latest version is now in the repo! Enjoy
Also, if anyone wants a particular ayatana-related package to be included in the repo, just drop a note here.
Hey it's greatt! i just installed it, But it's not work i guess, it's said that i need to to enable support for message-indicator in kopete, kmail, quassel & konversation. Is there a patch so it can support message indicator? Sorry if i'm asking too much
Offline
Well, those apps need to support the plasma widget as well I don't use KDE so I'm not familiar with this whole "plasma" business, but I'll take a look. If they look patchable/packageable I'll include them in the repo.
It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)
Offline
Well, those apps need to support the plasma widget as well I don't use KDE so I'm not familiar with this whole "plasma" business, but I'll take a look. If they look patchable/packageable I'll include them in the repo.
^^ thanks once again...
Offline
Little question: What does plasma-message-indicator do? I searched the web but I could not find anything. Kopete and Kmail can show messages like new mails etc. through KDE's notification system or colibri (which I prefer), so whats so special on this plasmoid?
Best regards!
Offline
Little question: What does plasma-message-indicator do? I searched the web but I could not find anything. Kopete and Kmail can show messages like new mails etc. through KDE's notification system or colibri (which I prefer), so whats so special on this plasmoid?
Best regards!
Well, it's grouping kopete, kmail, quassel or konversation into one, inside the message indicator. So it can save a lot of space in your system tray.
Offline
Ahh ok so you have one icon, that represents these applications and you can control them through this one icon. Sounds nice. Thanks!
Offline
Offline
I'm here, but I did't looked this forum for a week…
@dcc24: I think it would better to work together on packages in order to provide the best quality packages for Arch Linux users.
The main reason why I don't use the latest versions in my repo is that the development of Ayatana packages are adjusted to Ubuntu's release circle. This means that after Canonical released Ubuntu Maverick Meerkat, they started a rapid development process. During this process they use development releases of other packages as dependences, make ABI changes frequently, and frequently release developer snapshots. This makes very hard to maintain a stable and up to date system.
My solution for that is provide a stable repo with packages from the latest Ubuntu release, and provide a separated testing repo for users who really want to use/test/fix the latest packages. Now I updated all packages to the latest releases in this repo: indicators are works well, but Unity 2D still not works. Unfortunately my repo is on a free hosting server with many limitations, which cause problems, so I will move them as soon as I found a better place.
About third party indicators (indicator-cpufreq, indicator-feed…): these "indicators" are not true indicators. They are very similar to the panel applets, the only difference is they shown on indicator area instead of notification area. I may add some of them to my repo also, but I don't have time yet.
Offline
@City-busz: I agree, we should work together on this. I have a lot of disk space and bandwith on that machine, so I'll gladly provide access.
The main reason why I don't use the latest versions in my repo is that the development of Ayatana packages are adjusted to Ubuntu's release circle. This means that after Canonical released Ubuntu Maverick Meerkat, they started a rapid development process. During this process they use development releases of other packages as dependences, make ABI changes frequently, and frequently release developer snapshots. This makes very hard to maintain a stable and up to date system.
I realized this and I know it's a good way of doing this. What I did in my repo, is to basically create some patches (or do some sed magic) to make sure those ABI changes are shaped into compatibility for Arch. Yes, this makes packaging and maintaining much harder (I have A LOT of patches in the repo), but it also provides more up-to-date versions of everything.
Unfortunately my repo is on a free hosting server with many limitations, which cause problems, so I will move them as soon as I found a better place.
Once again, you can use my server and I can provide ssh access. The server runs Arch as well, so in an emergency, it can serve as a buildbox.
About third party indicators (indicator-cpufreq, indicator-feed…): these "indicators" are not true indicators. They are very similar to the panel applets, the only difference is they shown on indicator area instead of notification area. I may add some of them to my repo also, but I don't have time yet.
I realize that. However, after I posted here that I'm doing a repo myself, a couple of people messaged me to ask to package several of these pseudo-indicators. As long as people are interested, I'm willing to maintain them.
So, if it's ok with you as well, we can divide the ayatana packages between us, so it's much easier to maintain them.
It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)
Offline
Seems there is no indicator-appmenu in dcc24's repo?
Offline