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 view a package at a given revision:

• When I visit /package/read/xyz?rev=yyy I should be shown package at revision yyy
• package history page should provide links to these pages

Cost: 2h