Ticket #176 (closed enhancement: duplicate)
Package dependencies
Reported by: | dread | Owned by: | dread |
---|---|---|---|
Priority: | critical | Milestone: | |
Component: | ckan | Keywords: | |
Cc: | Repository: | ||
Theme: |
Description (last modified by rgrp) (diff)
(Related to ticket:169 - Package derivations)
A '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.)
e.g. london-traffic-visualisation depends on road-map
'Dependency' relationship is:
- directional
- many:many
- stateful
'dependency' table columns:
- id (primary key)
- dependent (foreign key)
- dependency (foreign key)
Further tickets:
- WUI - package view - have list of dependencies (do not need to list packages which depend on this one)
- WUI - package edit form - new option to say 'depends on' (no need for 'has dependent package')
- REST api - expose reading and writing 'depends on' property.
Issues
- How do we deal with dependency at a particular version?
Change History
comment:2 Changed 4 years ago by rgrp
- Description modified (diff)
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?
comment:5 Changed 4 years ago by dread
- Status changed from new to closed
- Resolution set to duplicate
Covered in ticket:253
Note: See
TracTickets for help on using
tickets.