Changes between Version 4 and Version 5 of YumFuture

Show
Ignore:
Author:
james (IP: 65.172.155.230)
Timestamp:
05/17/11 21:40:51 (7 years ago)
Comment:

Update the TODO list

Legend:

Unmodified
Added
Removed
Modified
  • YumFuture

    v4 v5  
    1 = Fedora16-17 and rhel7 Yum Goals
     1= Things that will probably happen to Yum in the future
    22 
     3This is a rough list of the significant features that are "planned" for yum, this means that we are planning on these being done (but they aren't done yet, so buyer beware :). We've tried to put them into two groups of difficulty but this is based on how much time it'll take to implement that particular feature. 
    34 
    4  * C-API  
    5     - Hard  
    6  * Parallel Downloading 
    7     - medium 
    8  * external call for downloads  
    9     - coupled with parallel downloading 
    10  * libs from plugins  
    11     - medium 
    12  * event notification/querying (traps/events/querying)  
    13     - could be hard - depending on the querying 
    14  * repo deltas - requires repodata format change  
    15     - could be gotten for free. 
    16  * repodata smaller/changing/format change  
    17     - potentially big change 
    18  * detached x509 sigs for pkg signatures  
    19     - requires lots of infrastructure/releng cooridination 
    20  * python 3 support?  
    21     - ??? 
    22  * documentation of our public interfaces  
    23     - not hard - time consuming 
    24  * make the user feel the impact of the yum/transaction lock less often  
    25     - medium 
    26  * weakdependencies (in metadata)  
    27     - not hard 
    28  * replacing the depsolver?  
    29     - involved/hard 
     5== 2011 Goals == 
    306 
     7 * '''HARD''' 
     8   * Adding a "simple" C-API to allow you to install/update/remove/query yum. Simple in this sense is "coverage", as in you should be able to do "simple" things. 
    319 
    32   
     10 * '''MEDIUM''' 
     11   * General maintainance, this includes all the smaller projects that don't make this list and bug fixes etc. 
     12   * Make the user feel the impact of the yum/transaction lock less often, and the user/root split (some of this is tied with background downloads etc.). 
     13   * Weak dependencies (in repo. metadata). There are multiple parts to this, and some of it requires distro. rel-eng work. This is just for the yum parts (so it might not actually be usable anyway :). 
     14   * Saving a bunch more data in history: 
     15     * A lot of the rpmdb/yumdb data, this will almost certainly hang off of pkgtup+checksum 
     16     * Possible we'll save some updateinfo, Eg. CVEs/BZs/security. 
     17   * Merged updateinfo, and probably creating some core updateinfo API. 
     18   * Better support for simple/"blocked" transactions: 
     19     * Improve load-ts to make it fail if the end rpmdb is different (much more assurance that everything is identical to a test run). 
     20     * Something like the "updater" plugin (http://james.fedorapeople.org/yum/plugins/updater.py), or yum-safe-update (https://github.com/timlau/YumTools/blob/master/yum-safe-update/yum-safe-update.py). 
     21 
     22== Longer term. Goals == 
     23 
     24These are the things people might want us to do for 2011, but are not guaranteed to happen. Some _might_, some are much more unlikely to happen due to time/etc. If you want to see something move from here to the above list, you probably need to speak to someone with the power to make it happen (or do it, and provide us patches :). 
     25 
     26 * '''HARD''' 
     27   * Revamp downloading, again. 
     28      * Parallel Downloading. 
     29      * Background downloading. 
     30      * External calls for downloads (isolating the install code from the download code etc.). 
     31   * Event notification/querying (traps/events/querying). This might be only '''MEDIUM''', depending on the required features. 
     32   * Repo. metadata overhaul: 
     33     * Repo. metadata deltas. 
     34     * Repo. metadata format change (should get it smaller/less to download). 
     35   * Repo. detached x509 sigs for pkg signatures, and repomd.xml. This requires significant work in non-yum parts (Eg. distro. rel-eng). 
     36   * Replacing the depsolver. 
     37 
     38 * '''MEDIUM''' 
     39   * Allow plugins to provide "library" like functions. 
     40   * Repo. metadata "xz" compression. Possible to switch to XML metadata, for download efficiency. 
     41   * Python 3 support. 
     42   * Documentation of at least our public interfaces. This isn't really hard, but to do fullish coverage it would be time consuming.  
     43   * Storage for "verify", so you can "store" config. changes etc. (see the puppet usage etc.) 
     44   * Installed groups ... groups as objects / whatever. 
     45   * Show in list_trans/history any pkgtups we didn't find from load-ts/undo/rollback. Maybe add excludes too.