You are not logged in.
I may be right that the AUR version does NOT need/depend on libgnome-keyring?
https://aur.archlinux.org/packages.php?ID=38057
I'm certainly no guru yet i do love no gnome whatsoever, horrid for me enough
that there's mention of pulse on my system.
Anyways, no matter... though could someone tell me if there'll be repercussions
avoiding the libgnome-keyring by using AUR git version.
i'd rather the usual pacman repo msmtp though can't do libgnome-keyring.
that said if it just one file somewhere that could be ok though gnome does have it's tentacles.
I'm being silly perhaps?
-sigh-
Last edited by tweed (2012-07-06 11:13:27)
Offline
It was added in a couple of months back:
https://projects.archlinux.org/svntogit … 0620cd4ded
As a result of this bug report:
https://bugs.archlinux.org/task/27435
It seems more like a dependancy than a makedepend to me, as you cannot remove it post build (but I probably just don't correctly understand the distinction)...
# edit: it's a split package, hence the makedepends.
Offline
thank you Sir!
So, as i recall I can download the package parts and compile myself.
leaving off both of these perhaps.
+ depends=('gsasl' 'libgnome-keyring')
will make post [SOLVED] after a think.
wow, many thanks!
Last edited by tweed (2012-07-06 10:08:15)
Offline
I am not sure why libgnome-keyring is a default for a package like this...
You can disable it with:
./configure --without-gnome-keyring --prefix=/usr --sysconfdir=/etcIt seems to me, though, that it would be more consistent with the Unix way to have people
that want gnome-keyring support to build it in themselves, rather than making it the default.
Offline
libgnome-keyring is a tiny library that brings in few dependencies (and nothing gnome related...). Its features are not used by msmtp unless it is set up to do so. So adding this as a dependency is really not intrusive to anyone who actually thinks about it... BUT IT HAS GNOME IN ITS NAME!
Offline
BUT IT HAS GNOME IN ITS NAME!

Offline