Re: [gentoo-dev] Unify keyring related USE flags

2014-11-13 Thread Pacho Ramos 
El dom, 12-10-2014 a las 10:38 +0200, Pacho Ramos escribió:
 El dom, 12-10-2014 a las 00:13 +0400, Alexander Tsoy escribió:
 [...]
   
   I think we should simply have a keyring USE flag to enable what most
   people will want - keyring support.
  
  Some apps have optional support for both kwallet and gnome-keyring
  (e.g. darktable, subversion). So I'm not sure you can leave a single
  USE flag.
  
 
 Maybe for them we could have an exception or review them as they also
 look to be a bit strange. For example, for concrete case of subversion
 looks like it's using gnome-keyring and kde, that looks a bit
 inconsistent to me. We could use gnome and kde for example :/. Or
 have a keyring USE flag and, then gnome and kde behind that USE
 
 

any updates on this? :)

Re: [gentoo-dev] Unify keyring related USE flags

2014-11-13 Thread Alexander Tsoy 
В Thu, 13 Nov 2014 11:53:56 +0100
Pacho Ramos pa...@gentoo.org пишет:

 El dom, 12-10-2014 a las 10:38 +0200, Pacho Ramos escribió:
  El dom, 12-10-2014 a las 00:13 +0400, Alexander Tsoy escribió:
  [...]

I think we should simply have a keyring USE flag to enable what most
people will want - keyring support.
   
   Some apps have optional support for both kwallet and gnome-keyring
   (e.g. darktable, subversion). So I'm not sure you can leave a single
   USE flag.
   
  
  Maybe for them we could have an exception or review them as they also
  look to be a bit strange. For example, for concrete case of subversion
  looks like it's using gnome-keyring and kde, that looks a bit
  inconsistent to me. We could use gnome and kde for example :/. Or
  have a keyring USE flag and, then gnome and kde behind that USE
  
  
 
 any updates on this? :)
 

I don't know anything about kwallet, but gnome-keyring is useful
outside of GNOME. So I don't like the idea of hiding gnome-keyring
behind gnome use flag.

-- 
Alexander Tsoy

Re: [gentoo-dev] Unify keyring related USE flags

2014-11-13 Thread Pacho Ramos 
El jue, 13-11-2014 a las 14:12 +0300, Alexander Tsoy escribió:
 В Thu, 13 Nov 2014 11:53:56 +0100
 Pacho Ramos pa...@gentoo.org пишет:
 
  El dom, 12-10-2014 a las 10:38 +0200, Pacho Ramos escribió:
   El dom, 12-10-2014 a las 00:13 +0400, Alexander Tsoy escribió:
   [...]
 
 I think we should simply have a keyring USE flag to enable what most
 people will want - keyring support.

Some apps have optional support for both kwallet and gnome-keyring
(e.g. darktable, subversion). So I'm not sure you can leave a single
USE flag.

   
   Maybe for them we could have an exception or review them as they also
   look to be a bit strange. For example, for concrete case of subversion
   looks like it's using gnome-keyring and kde, that looks a bit
   inconsistent to me. We could use gnome and kde for example :/. Or
   have a keyring USE flag and, then gnome and kde behind that USE
   
   
  
  any updates on this? :)
  
 
 I don't know anything about kwallet, but gnome-keyring is useful
 outside of GNOME. So I don't like the idea of hiding gnome-keyring
 behind gnome use flag.
 

But people wanting keyring support in gnome will know need to remember
to also enable libsecret (that will replace gnome-keyring at some
point). That is the main reason for suggesting the change. That and also
that kde USE flag is being used for keyring support in KDE
environment, and that can look a bit incoherent.

Having a more general keyring USE flag people could enable and, for
cases with multiple support, allow to switch between providers on KDE
and GNOME depending on their kde gnome USE flags looks to solve it
for me :/

Re: [gentoo-dev] Unify keyring related USE flags

2014-10-12 Thread Pacho Ramos 
El dom, 12-10-2014 a las 00:13 +0400, Alexander Tsoy escribió:
[...]
  
  I think we should simply have a keyring USE flag to enable what most
  people will want - keyring support.
 
 Some apps have optional support for both kwallet and gnome-keyring
 (e.g. darktable, subversion). So I'm not sure you can leave a single
 USE flag.
 

Maybe for them we could have an exception or review them as they also
look to be a bit strange. For example, for concrete case of subversion
looks like it's using gnome-keyring and kde, that looks a bit
inconsistent to me. We could use gnome and kde for example :/. Or
have a keyring USE flag and, then gnome and kde behind that USE

[gentoo-dev] Unify keyring related USE flags

2014-10-11 Thread Pacho Ramos 
Hello

I am wondering about current status of keyring related USE flags:
- gnome-keyring USE is listed as global USE
- libsecret is a local USE
- wallet is local (only used by one package now)

I think we should simply have a keyring USE flag to enable what most
people will want - keyring support.

What do you think? I am not sure what kind of USE flags are other
desktops but Gnome/MATE using :S

Thanks a lot

Re: [gentoo-dev] Unify keyring related USE flags

2014-10-11 Thread Alexander Tsoy 
В Sat, 11 Oct 2014 17:02:20 +0200
Pacho Ramos pa...@gentoo.org пишет:

 Hello
 
 I am wondering about current status of keyring related USE flags:
 - gnome-keyring USE is listed as global USE
 - libsecret is a local USE
 - wallet is local (only used by one package now)

Err.. wallet USE flag is completely unrelated. This wallet is for
bitcoins, it's not a keyring for passwords. :)

There are also gnome and kde USE flags. Note that the following
command doesn't catch multiline USE-conditional dependencies.

$ find . -type f -name *.ebuild -exec egrep -e 'kde\?.*kwallet' -e 
'gnome\?.*gnome-keyring' '{}' \+
./dev-vcs/subversion/subversion-1.8.9.ebuild:   kde? ( kde-base/kwalletd )
./dev-vcs/subversion/subversion-1.8.10.ebuild:  kde? ( kde-base/kwalletd )
./dev-vcs/subversion/subversion-1.7.18.ebuild:  kde? ( kde-base/kwalletd )
./media-gfx/darktable/darktable-1.2.3.ebuild:   kde? ( kde-base/kwalletd )
./media-gfx/darktable/darktable-1.4.1-r1.ebuild:kde? ( 
kde-base/kwalletd )
./media-gfx/darktable/darktable-1.4.2.ebuild:   kde? ( kde-base/kwalletd )
./media-gfx/darktable/darktable-1.4.ebuild: kde? ( kde-base/kwalletd )
./media-gfx/darktable/darktable-.ebuild:kde? ( kde-base/kwalletd )
./media-sound/cantata/cantata-1.3.3.ebuild: kde? ( $(add_kdebase_dep 
kwalletd) )
./media-sound/cantata/cantata-1.3.4.ebuild: kde? ( $(add_kdebase_dep 
kwalletd) )
./net-fs/smbnetfs/smbnetfs-0.5.3a.ebuild:   gnome? ( 
gnome-base/gnome-keyring:= )
./net-fs/smbnetfs/smbnetfs-0.5.3b.ebuild:   gnome? ( 
gnome-base/gnome-keyring:= )
./net-im/gajim/gajim-0.15.4.ebuild: gnome? ( gnome-keyring )
./net-im/gajim/gajim-0.15.4.ebuild: kde? ( kde-base/kwalletmanager )
./net-im/gajim/gajim-0.16.ebuild:   gnome? ( gnome-keyring )
./net-im/gajim/gajim-0.16.ebuild:   kde? ( kde-base/kwalletmanager )
./www-client/qupzilla/qupzilla-1.6.5.ebuild:kde? ( kde-base/kwalletd:4 )
./www-client/qupzilla/qupzilla-1.6.6.ebuild:kde? ( kde-base/kwalletd:4 )
./www-client/qupzilla/qupzilla-1.8.0.ebuild:kde? ( kde-base/kwalletd:4 )

 
 I think we should simply have a keyring USE flag to enable what most
 people will want - keyring support.

Some apps have optional support for both kwallet and gnome-keyring
(e.g. darktable, subversion). So I'm not sure you can leave a single
USE flag.

 
 What do you think? I am not sure what kind of USE flags are other
 desktops but Gnome/MATE using :S
 
 Thanks a lot
 

-- 
Alexander Tsoy