forked from manatools/dnfdragora
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathTODO
42 lines (36 loc) · 2.38 KB
/
TODO
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
This file is meant to get a list of things that should be hopefully implemented or fixed
as soon as possible.
== Near term targets ==
=== Critical ===
* Keys management. At the very least, we need to be able to query and verify package signing keys.
* Repository update, TransactionProgress::update gets wrong information
e.g. the number of file (always 1) and not its size so dowload progress
bar is always wrong (need upstream interaction)
* Repository management (enabling and disabling repositories)
* String localization, all is ready but gettext is not used
=== Important ===
* libyui, we need to ask for a patch review concerning YItem selection needed to manage
package selection and released on github by anaselli.
* Add system configuration file for configuring the application per distro/system.
* Theme management icons are taken from mageia system. A default theme should
be provided.
* Group management, upstream rpm seems not to manage groups any more at least in
the way mageia does, we should allow a configuration key to enable/disable mageia
behaviour and manage group in a standard way for other systems.
=== Nice to have ===
* Add a user specific configuration file for saving user preferences.
* Modifying repository configuration to override settings per repository.
== Medium term targets ==
* Handle solution errors. In the event that there's a dependency problem detected, we should
offer the user a way to resolve it from within the UI so that it can be resolved.
* Offer weak dependency options, handling both forward and reverse dependencies.
With weak dependencies, we should offer a way for the user to select whether to install
recommended/supplementary packages, add suggested/enhancing packages to the transaction, etc.
* Handle multiple provider case. When something is provided by multiple packages, we need to be
able to offer the user a choice and indicate a sane default based on the system package
set and the transaction itself.
== Long term targets ==
* Handle complex dependencies. If there are conditional dependencies, we should offer ways to
select from the set of options (in the case with Requires with "or") or offer ways to enable
additional functionality (in the case where Requires only activate if something is installed).
If you want to help in any of this items, or new ones please contact us