| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
https://mesonbuild.com/Reference-manual_functions.html#library
|
|
|
|
|
|
|
|
| |
Existing code produces these errors:
| gcr/meson.build:61:0: ERROR: Unable to get the path of a not-found external program
| gcr/meson.build:101:5: ERROR: Unknown variable "ssh_add_path".
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gcr historically consisted of 2 high-level parts: `gcr-base` and
`gcr-ui`. `gcr-base` contains the core classes and interfaces to deal
with crypto-related items (e.g. `GcrCertificate`), while `gcr-ui`
contained GTK widgets to show those items (e.g. `GcrCertificateWidget`).
Now: with the move to gcr4, it's becoming more and more clear to that this isn't really a path forward:
On one hand, GTK4 has transitioned from a platform toolkit (usually
GNOME was the primary target) to one that allows you to build your
platform on top (e.g. libadwaita, libgranite, or your very own). Kepeing
that in mind, having "GTK-based" widgets for use in general purpose
doesn't really make sense, since it will always look out touch on
platforms
On the other hand, widgets are usually more faster-moving targets in
both looks as well as API than an actual library, so in practice gcr-ui
has a different lifecycle than gcr-base.
Finally, @tintou has been doing an awesome effort to implement an API
that allows consumers to write their own widgets, without having to deal
with asn1 decoding etc. At this point, I think the certificate widget is
likely the only widget we're seeing interest in.
As such, this commit drops gcr-gtk3 and gcr-gtk4 as libraries. There's
still a gcr-viewer debugging tool as a troubleshooting/debugging tool,
that's it.
See https://gitlab.gnome.org/GNOME/gcr/-/issues/100 for the related
discussion.
|
|
|
|
|
|
| |
Allows to use the same code-path for both GTK3 and GTK4.
Also allow any library-user to reimplement it with the toolkit of its choice or
to adapt it when a different styling is required (e.g. with libadwaita).
|
|
|
|
|
|
|
|
|
|
| |
gck provided some APIs that made working with lists of `GObject`s
easier. GLib has for a long time added API that works well enough for
the same use case, like `g_list_copy_deep()`, `g_list_free_full()` and
more recently also `g_clear_list()`, so use those instead.
This commit also bumps the required GLib version to a more modern 2.64
(which is needed for the `g_clear_list()` API).
|
|
|
|
|
|
|
|
|
|
|
| |
Icons are problematic to provide within gcr, as different DEs that are
using it, have different expectations what such an icon should look
like: one wants it to be colorful, another wants it to be monochrome,
yet another wants everything skeumorphic etc.
Let's not deal with this in gcr4 and drop any icons. If applications
want to provide an icon, they can do that themselves much better then we
ever can.
|
|
|
|
|
| |
The only known consumer is Seahorse, which should either just ship it
itself, or it would need to learn to parse e.g. gpg.conf
|
|
|
|
|
|
| |
`gcr-prompter` got removed in the gcr4 migration, so keeping these
doesn't make sense in any case. If we decide to bring back
`gcr-prompter`, we can still revert this commit too.
|
|
|
|
| |
That way, we don't conflict with the translations for gcr3
|
|
|
|
|
|
| |
There are no desktop files, and only GTK3 builds have icons.
Fixes https://gitlab.gnome.org/GNOME/gcr/-/issues/97
|
| |
|
|
|
|
| |
It's deprecatedd for `dep.get_variable()`
|
| |
|
|
|
|
|
|
|
| |
We should use the pkg-config variable of the `dbus-1` package to check
where we should install our D-Bus services, but we also need to make
sure we don't pollute anything outside of $prefix, so make sure to get
that case as well.
|
|
|
|
|
| |
Allows us to drop our custom post-install script, and fixes some known
issues with it.
|
|
|
|
| |
That'll allow us to use some new goodies from Meson.
|
| |
|
|
|
|
| |
It is now gcr4 and gck2.
|
|
|
|
| |
Signed-off-by: Corentin Noël <corentin.noel@collabora.com>
|
| |
|
| |
|
|
|
|
| |
Also remove the post-install symlinks
|
| |
|
|
|
|
|
|
| |
Do not rely on major_version to manually create the library names.
Make sure to be consistent and use a single variable for all the library names
and folder mentions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gtk-doc has been slowly dying for the past few years. With gi-docgen we
have a clear successor in sight to replace the voodoo magic one needs to
get the whole documentation setup.
See the [gi-docgen tutorial] for more info on how the system works.
Since we're now only the C compiler (and GIR) parse the C code, that
means we can also get rid of all the special escapes for the # character
in PKCS#11.
[gi-docgen tutorial]: https://gnome.pages.gitlab.gnome.org/gi-docgen/tutorial.html
|
| |
|
| |
|
|
|
|
|
|
| |
This port the ssh-agent support provided as a sub-daemon in
gnome-keyring, as a standalone binary, so that it can easily be
managed through systemd.
|
| |
|
|
|
|
|
|
|
|
|
| |
GDK provides an interface to the _xdg-foreign_ protocol extension, which
exactly allows to export a handle that another window can use to set
itself transient to.
Also bump the minmal GTK version to 3.22, since that is the version that
adds the necessary methods to do this in GDK.
|
|
|
|
| |
This avoids circular dependencies, such as gcr -> gpg2 -> pinentry -> gcr
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After switching the build system from autotools to meson, gnome-keyring
can no longer unlock ssh keys.
sign_and_send_pubkey: signing failed: agent refused operation
user@host's password:
Running 'truss' on 'gnome-keyring-daemon' shows that it fails to execute
'gcr-ssh-askpass' file.
write(2,"ssh_askpass: exec(<prefix>/libexec/gcr/gcr-ssh-askpass): No such file or directory\n",105) ERR#9 'Bad file descriptor'
To keep both autotools and meson builds working, change the definition
in meson build to be the same as autotools build.
|
|
|
|
|
|
| |
GLib 2.44 adds `G_DEFINE_AUTOPTR_CLEANUP_FUNC` and
`G_DECLARE_FINAL_TYPE` which we can use to cleanup the codebase and to
let others use our types with `g_autoptr()`.
|
| |
|
|
|
|
|
|
| |
Meson isn't setting the "Requires" field, so we have to do it manually.
Since we don't want to specify each dependency in `glib_deps` as a
dependency, we also give each a separate variable.
|
|
|