| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Conceptually similar to the previous commit, except it didn't crash
before, just didn't display anything.
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
|
|
|
|
|
|
|
| |
flatpak_dir_load_deployed() can fail and return NULL. If that happens,
there is a semi-installed but broken app, and we should show a warning
rather than crashing.
Resolves: https://github.com/flatpak/flatpak/issues/5293
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
|
|
|
|
|
|
|
| |
To make indentation work with less effort. The modeline was copied from
libostree with minor modification and the .editorconfig from GLib.
The advantage of having both a modeline and an editorconfig is we can
work out of the box on more editor setups, and the modeline allows us to
specify the style with a lot more fine grained control.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Recent Meson versions have warnings if you add the subprojects
directory as an include path, because the way Meson wants to consume
subprojects is by the subproject's build system producing a Meson
dependency object that encapsulates its include directory. Flatpak
doesn't have a Meson build system yet, but I'm working on that.
libglnx seems to be set up to have the libglnx directory be its include
path instead: for example, ostree (by the author of libglnx) already
uses "libglnx.h" or <libglnx.h> everywhere. Do the same here.
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The man page states that the --all option for the list command includes
runtime extensions (e.g. that end in .Locale or .Debug) and this is the
case. When --all is omitted, we only show such extensions when the thing
they extend is not already in the list. However when you run a command
like "flatpak list --runtime --columns=application,branch", you get a
list that excludes runtime locale extensions but includes app locale
extensions, since the corresponding apps are not in the list despite
presumably being installed. This doesn't seem like the right behavior,
so tweak the logic so that app locale extensions are excluded when --all
is omitted and --runtime is used.
Strictly speaking the "extension-of" information is not guaranteed to be
present in the deploy data (which acquires it from the metadata), but in
practice it seems to be present for all but Sources extensions, and I
think it should be considered required since we are already using it to
implement functionality elsewhere in Flatpak:
https://github.com/flatpak/flatpak/issues/4585
|
| |
|
|
|
|
|
| |
Fixes: https://github.com/flatpak/flatpak/issues/4223
Fixes: https://github.com/flatpak/flatpak/issues/4224
|
|
|
|
|
| |
We now converted most of these and removed the non-prefixed functions,
so rename them back.
|
|
|
|
| |
Then convert all callers
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
These now take (optional) string length args:
flatpak_id_has_subref_suffix()
flatpak_levenshtein_distance()
flatpak_is_valid_name()
flatpak_is_valid_branch()
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, if you run:
flatpak remote-ls flathub --app-runtime=com.endlessm.Platform//eos3.2
you see no apps (correct) but hundreds of runtimes. This is inconsistent
with the documentation for the '--app-runtime' option, which says:
> List applications that use the given runtime
To fix this, default to not showing runtimes if '--app-runtime' is
given. This is consistent with the behaviour if just '--app' is
specified. If you run 'flatpak list --app-runtime=com.example.Foo
--runtime' then you get apps using that runtime, plus all other
runtimes, which seems fair enough to me.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of combining name and comment we split them into two columns.
We also disable the comment column by default for list and remote-ls
as it is very poor in long tables. However, it is still there for search
where it seems more useful.
Also, the Application column title changed to Application ID to make
it clearer what it is compared to the "Name" column.
Closes: #2852
Approved by: alexlarsson
|
|
|
|
|
| |
Closes: #2850
Approved by: matthiasclasen
|
|
|
|
|
| |
Closes: #2850
Approved by: matthiasclasen
|
|
|
|
|
|
|
|
| |
Additionally flatpak_table_printer_set_columns now takes a boolean
to say whether the arguments in use are the default.
Closes: #2850
Approved by: matthiasclasen
|
|
|
|
|
|
|
| |
This is useful information, so we should allow showing it.
Closes: #2815
Approved by: alexlarsson
|
|
|
|
|
|
|
| |
It was looking at the wrong part of the ref...
Closes: #2765
Approved by: mwleeds
|
|
|
|
|
|
|
|
| |
I had to make a few manual edits but other than those the changes look
reasonable.
Closes: #2715
Approved by: matthiasclasen
|
|
|
|
|
|
|
|
|
|
|
|
| |
Move expand and ellipsize to the Column struct,
and change flatpak_table_printer_set_column_titles
to flatpak_table_printer_set_columns that sets up
not just the title, but also expand and ellipsize.
Update all callers.
Closes: #2460
Approved by: alexlarsson
|
|
|
|
|
|
|
|
|
| |
We were inadvertedly adding extra columns when
trying to set existing columns as ellipsizable.
Oops.
Closes: #2460
Approved by: alexlarsson
|
|
|
|
|
|
|
|
| |
Call flatpak_complete_columns for every command
that understands --columns.
Closes: #2445
Approved by: alexlarsson
|
|
|
|
|
|
|
|
|
| |
When the --app-runtime option was added to the list command, -a was made
its shortcut, but this already belongs to --all, so return it to the
latter.
Closes: #2543
Approved by: matthiasclasen
|
|
|
|
|
|
|
| |
The options column shows eol messages, which are long.
Closes: #2497
Approved by: matthiasclasen
|
|
|
|
|
|
|
| |
If we have nothing to print, don't print a stray newline.
Closes: #2461
Approved by: matthiasclasen
|
|
|
|
|
| |
Closes: #2448
Approved by: alexlarsson
|
|
|
|
|
|
|
|
| |
I think this makes a lot more sense than ellipsizing in the middle.
Most app ids start with a common prefix after all.
Closes: #2448
Approved by: alexlarsson
|
|
|
|
|
|
|
|
| |
This preserves relevant information at the beginning
and the end.
Closes: #2448
Approved by: alexlarsson
|
|
|
|
|
|
|
|
| |
The application IDs also tend to be long,
so ellipsize that column as well.
Closes: #2448
Approved by: alexlarsson
|
|
|
|
|
| |
Closes: #2450
Approved by: alexlarsson
|
|
|
|
|
| |
Closes: #2450
Approved by: alexlarsson
|
|
|
|
|
|
|
|
| |
Without this its impossible to tell apart e.g. multiple
runtimes for different arches.
Closes: #2409
Approved by: alexlarsson
|
|
|
|
|
|
|
|
| |
Its really wasteful to have headers much wider than the
items in the column.
Closes: #2409
Approved by: alexlarsson
|
|
|
|
|
| |
Closes: #2409
Approved by: alexlarsson
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a version to the deply data format, assuming that if
there is no version then it is 0. Also extends all loaders so that
it can specify a required version, with the goal that most users
are fine with old versions, but if you need more recent we have
a (costly) conversion process to upgrade (will be added later).
The library and the flatpak list/info commands require the most
current version for full info, all other users can use any version.
Also, as part of this we now pass the ref to flatpak_load_deploy_data()
as this will be needed later for the backwards compat support.
Closes: #2409
Approved by: alexlarsson
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add new description, installation and version columns,
revise the list of default columns, and make use of the
new ellipsization support in the table printer.
This gets us closer to the design in
https://github.com/flatpak/flatpak/wiki/CLI-experimental-design
Closes: #2409
Approved by: alexlarsson
|
|
|
|
|
| |
This is useful information when debugging language-related
issues.
|
|
|
|
|
|
|
| |
This is more flexible than --show-details.
Closes: #2090
Approved by: alexlarsson
|
|
|
|
|
|
|
|
| |
This lets you use list --app --app-runtime=org.gnome.Platform//3.24
to see which apps on your system still depend on this old runtime.
Closes: #2175
Approved by: alexlarsson
|
|
|
|
|
| |
Closes: #1870
Approved by: alexlarsson
|
|
|
|
|
|
|
|
| |
This makes info, list, remotes, and search work if there is no
system flatpak repo. Before it failed with EPERM.
Closes: #1742
Approved by: alexlarsson
|
|
|
|
|
|
|
| |
This is the start of the merging of lib/* into common/*
Closes: #1706
Approved by: alexlarsson
|
|
|
|
|
| |
Closes: #1566
Approved by: alexlarsson
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some builtin flatpak commands work on a single installation, and others
work on multiple installations (such as the remotes command that lists
both system and user remotes). Currently flatpak_option_context_parse()
only supports returning one installation to its caller, and any commands
that want to support multiple installations have to implement that
themselves which leads to a lot of code duplication.
This commit changes flatpak_option_context_parse() to take three new
flags:
* FLATPAK_BUILTIN_FLAG_ONE_DIR maintains the old behavior by
returning one installation (i.e. user if --user was passed, system if
--system, etc.).
* FLATPAK_BUILTIN_FLAG_STANDARD_DIRS will get all the installations
specified by the options, or the user and system ones if none were.
* FLATPAK_BUILTIN_FLAG_ALL_DIRS includes non-default system
installations along with the user and system ones if none were
specified.
These flags also affect what options are parsed and whether the
directories are ensured to exist, so it makes sense in some
circumstances for callers to pass a NULL out_dirs even when not using
FLATPAK_BUILTIN_FLAG_NO_DIR.
This commit also changes all the callers of
flatpak_option_context_parse() so they maintain their behavior. The only
functional change introduced by this is that using --installation
multiple times for commands that only support one now leads to an
error emitted by flatpak rather than by g_option_context_parse().
A follow-up commit will use this refactoring to make many commands
behave more intelligently in determining which installation to use.
Closes: #1205
Approved by: alexlarsson
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It's easy to end up with multiple flatpak installations on a system, and
it's not always clear which one(s) flatpak is using. So this commit adds
some debug output in some cases when flatpak opens an installation
directory such as /var/lib/flatpak. This is especially important for
people who build flatpak themselves because if you omit --prefix=/usr
or use --with-system-install-dir your flatpak will look in non-standard
locations like /usr/local/var/lib/flatpak.
If we were to print this every time a flatpak directory is opened, it
would flood the log. So instead add a utility function and use it
strategically. Many flatpak commands will log the directory when they
use flatpak_option_context_parse(), others in
flatpak_find_deploy_for_ref(), and for others the logging has been
added manually.
Closes: #1067
Approved by: alexlarsson
|
|
|
|
|
| |
org.foo.foo-bar extensions become org.foo.foo_bar.Locale, etc, so
we need to handle this properly.
|
| |
|