Re: [dev] libsecret implementation

2023-10-10 Thread Marko Bauhardt
Hi, > ... If it's not, and you don't have a say in the matter, > then there's obviously nothing you can do about it, no? Yes it's a piece of software we have to use. This piece has gnome keyring as their dependency. My hope was to define another implementation like https://github.com/grawity/secr

Re: [dev] libsecret implementation

2023-10-10 Thread stefan11111
>D-Bus is bloat in itself and should be avoided if possible, just like related >bloatware such as systemd. > >[1]: https://github.com/grawity/secretsd +1 I've yet to see a good reason to use dbus.

Re: [dev] libsecret implementation

2023-10-10 Thread Страхиња Радић
On 23/10/10 01:04PM, Страхиња Радић wrote: > It all depends on the degree of your agency over the choice of software and > over the software itself. If it's a program you wrote, then consider > switching > away from D-Bus to interfacing with a simpler/better/more traditional > solution, > like

Re: [dev] libsecret implementation

2023-10-10 Thread Страхиња Радић
On 23/10/10 10:33AM, Marko Bauhardt wrote: > Hi, > i have to use a program at work which requires libsecret - Secret > Service D-Bus client library. > Right now I'm using the gnome keyring implementation. > I would like to get rid of this implementation and use a more simpler > one, in other words

[dev] libsecret implementation

2023-10-10 Thread Marko Bauhardt
Hi, i have to use a program at work which requires libsecret - Secret Service D-Bus client library. Right now I'm using the gnome keyring implementation. I would like to get rid of this implementation and use a more simpler one, in other words without gnome/kde deps. Do you know any suckless alter