Custom Query (2152 matches)

Reported by rgrp, 5 years ago.

1. Given a url download from that url to disk
2. Given a package use download url to download to disk

Once on disk should uncompress (if necessary).

Details

• Should download either to tmp directory (defaulted in config) or a specified path on disk
• In download would like to support as many types of target urls as possible:
  1. Single files (usually compressed filesets but could be individual files)
  2. Index pages listing files to download
  3. Revision control repositories
  4. ...

This will obviously be a significant amount of work. Suggest:

1. Start off just supporting the first option.
2. Have something like a plugin system to handle new target types
3. Reuse existing work (e.g. easy_install and pip handle standard vcs such as svn, hg, git etc)

Cost: 1d

Reported by rgrp, 5 years ago.

This is better for long term sustainability, especially if we want to "push and pull" from unrelated repositories in the future.

Details:

• May wish to retain a number field updated in the usual incremental way (what's the cost/benefit here?)

Reported by rgrp, 5 years ago.

As a user i want to see a package at "version" X (NB: not revision X).

• When I visit e.g. /package/read/xyz?version=0.7 I should be shown package at version 0.7 (or a message saying no such version)
• Implementation:
  • Find revision for this version (search revision history for when version field was last 0.7)
  • Show pacakge at that revision (as in ticket:103)
• On history page also shows versions in list of revisions associated with the package