path: root/wiki/src/blueprint/additional_software_packages.mdwn
diff options
authorintrigeri <>2017-09-16 09:18:06 +0000
committerintrigeri <>2017-09-16 09:24:29 +0000
commitecb171284086931fe7276d3b04e6cadca5705568 (patch)
treead3237e1a64ba400d1bdff709af4c60f38abb5a3 /wiki/src/blueprint/additional_software_packages.mdwn
parent13cb21c0adaf68eefd53891753cefa2b1c9e40e5 (diff)
Blueprint: mention PackageKit (refs: #14594).
Diffstat (limited to 'wiki/src/blueprint/additional_software_packages.mdwn')
1 files changed, 7 insertions, 1 deletions
diff --git a/wiki/src/blueprint/additional_software_packages.mdwn b/wiki/src/blueprint/additional_software_packages.mdwn
index fc13025..36c50d1 100644
--- a/wiki/src/blueprint/additional_software_packages.mdwn
+++ b/wiki/src/blueprint/additional_software_packages.mdwn
@@ -21,7 +21,13 @@ Proposed user experience
1. When installing a new package, either through the command line or
through Synaptic, the user is asked whether she wants to make it
+persistent. XXX: long-term wise, we should probably focus on _GNOME
+Software_ instead of _Synaptic_; if something works for both, fine,
+but the PackageKit D-Bus interface might be easier to support than
+hooking APT/dpkg, so one option would be to only support installation
+& removal done via PackageKit (i.e. either with _GNOME Software_ or
+using `pkcon` on the command line) and not operations done directly
+with `apt` or _Synaptic_.
2. When removing a persistent package, the user is asked whether she
wants to remove it from the list of persistent packages.