Project

Profile

Help

Actions
Send by e-mail Copy link

Story #2040

closed

As a user, I can choose which package types to sync

Added by amacdona@redhat.com over 8 years ago. Updated over 3 years ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Target Release - Python:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

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.

Related issues

Related to Python Support - Story #2041: As a user, I can whitelist packages to sync with standard python syntaxMODIFIEDbizhang

Actions
Related to Python Support - Refactor #6930: Use Bandersnatch to perform package metadata fetching and filteringMODIFIEDgerrod

Actions
Actions
Copy link
 #1

Updated by amacdona@redhat.com over 8 years ago

  • Tracker changed from Issue to Story
Actions
Copy link
 #2

Updated by semyers over 8 years ago

  • 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.

Actions
Copy link
 #3

Updated by amacdona@redhat.com over 8 years ago

  • Sprint Candidate changed from No to Yes
Actions
Copy link
 #4

Updated by amacdona@redhat.com about 8 years ago

  • Sprint Candidate changed from Yes to No
Actions
Copy link
 #5

Updated by amacdona@redhat.com over 7 years ago

  • Sprint Candidate changed from No to Yes
Actions
Copy link
 #6

Updated by amacdona@redhat.com about 7 years ago

  • Sprint Candidate changed from Yes to No
Actions
Copy link
 #7

Updated by bizhang over 6 years ago

  • Tags Pulp 3 added
Actions
Copy link
 #8

Updated by amacdona@redhat.com over 6 years ago

  • Related to Story #2041: As a user, I can whitelist packages to sync with standard python syntax added
Actions
Copy link
 #9

Updated by amacdona@redhat.com over 6 years ago

Marking this as related to 2041. Not sure if we want to include package type information in the whitelist specifiers or not.

Actions
Copy link
 #10

Updated by bizhang over 6 years ago

  • Sprint/Milestone set to 3.0 GA
Actions
Copy link
 #11

Updated by bizhang over 6 years ago

Should this be per specifier? e.g. scipy bdist, Django bdist, pulp sdist

Or per sync: e.g. sync bdist for [Django, scipy, pulp]

Actions
Copy link
 #12

Updated by amacdona@redhat.com over 5 years ago

  • Sprint/Milestone deleted (3.0 GA)
Actions
Copy link
 #13

Updated by bmbouter over 5 years ago

  • Tags deleted (Pulp 3)
Actions
Copy link
 #14

Updated by dalley over 4 years ago

  • Related to Refactor #6930: Use Bandersnatch to perform package metadata fetching and filtering added
Actions
Copy link
 #15

Updated by gerrod over 3 years ago

  • Status changed from NEW to CLOSED - DUPLICATE
Actions
Send by e-mail Copy link

Also available in: Atom PDF