Changes between Initial Version and Version 2 of Ticket #176


Ignore:
Timestamp:
11/06/09 18:43:23 (4 years ago)
Author:
rgrp
Comment:

My suggestion here is that this ticket get taken to okfn-discuss/okfn-help. This isn't a trivial issue.

Do we go Debian (must exist in debian and to a name) or PyPI (very flexible, to name + version) route?

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #176

    • Property Type changed from defect to enhancement

  • Ticket #176 – Description

    initial v2  
    33A 'dependency' relationship can be applied from one package to another. It implies that a package requires the download or existence of another package which it 'depends on'. (Analogous to software package dependencies.) 
    44 
    5 e.g. 
    6 london-traffic-visualisation depends on road-map 
     5e.g. london-traffic-visualisation depends on road-map 
    76 
    87'Dependency' relationship is: 
    … …  
    1312'dependency' table columns: 
    1413 * id (primary key) 
    15  * source_package (foreign key) 
    16  * result_package (foreign key) 
    17  * description (markdown text) 
     14 * dependent (foreign key) 
     15 * dependency (foreign key) 
    1816 
    1917Further tickets: 
    2018 
    21  * WUI - package view - shows 'depends on package x' and 'dependent package y' with UML-like diagram of x -> this package -> y 
    22  * WUI - package edit form - new option to say it 'depends on' or 'has dependent package' and you select the appropriate package. 
     19 * WUI - package view - have list of dependencies (do not need to list packages which depend on this one) 
     20 * WUI - package edit form - new option to say 'depends on' (no need for 'has dependent package') 
    2321 * REST api - expose reading and writing 'depends on' property. 
     22 
     23=== Issues === 
     24 
     25 * How do we deal with dependency at a particular version?