Story #2040
closed
As a user, I can choose which package types to sync
Status:
CLOSED - DUPLICATE
Description
A user should be able to disable syncing of wheels or sdist, and possibly restrict the different compression (tar.gz, tar.bz2, .zip) that hold them. The primary use case for this is a user who primarily uses sdists because there can be many wheels for each sdist. This could expend a lot of unnecessary resources.
- Tracker changed from Issue to Story
- Groomed changed from No to Yes
As described, this sounds a lot like RPM's --skip repo option, which disabled syncing of different content unit types, like errata or drpms. I think this will be a little different for the python plugin, but from a usage perspective I think it makes sense to behave similarly when doing similar things.
This is probably a different story, but it might also be nice to be able to filter wheels by platform, so you can filter out the py2 wheels and only bring down py3, for example.
- Sprint Candidate changed from No to Yes
- Sprint Candidate changed from Yes to No
- Sprint Candidate changed from No to Yes
- Sprint Candidate changed from Yes to No
- Related to Story #2041: As a user, I can whitelist packages to sync with standard python syntax added
Marking this as related to 2041. Not sure if we want to include package type information in the whitelist specifiers or not.
- Sprint/Milestone set to 3.0 GA
Should this be per specifier? e.g. scipy bdist, Django bdist, pulp sdist
Or per sync: e.g. sync bdist for [Django, scipy, pulp]
- Sprint/Milestone deleted (
3.0 GA)
- Related to Refactor #6930: Use Bandersnatch to perform package metadata fetching and filtering added
- Status changed from NEW to CLOSED - DUPLICATE
Also available in: Atom
PDF
.