Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Break out the RPZ manipulation code #322

Open
remram44 opened this issue Sep 12, 2018 · 2 comments
Open

Break out the RPZ manipulation code #322

remram44 opened this issue Sep 12, 2018 · 2 comments
Assignees
@remram44
Labels
T-enhancement Type: En enhancement to existing code, or a new feature T-task Type: Something to be done, neither a bugfix nor an enhancement of the code
Milestone
2.0

Comments

@remram44
Copy link
Member

Providing a library for reading and manipulating RPZ bundles would be a good idea. It would also remove the duplicated files.

Goes with #192
@remram44 remram44 added T-enhancement Type: En enhancement to existing code, or a new feature T-task Type: Something to be done, neither a bugfix nor an enhancement of the code labels Sep 12, 2018
@remram44 remram44 added this to the 1.1 milestone Sep 12, 2018
@remram44
Copy link
Member Author

I plan to reorganize the PyPI packages even further for 2.0:

packages

Design notes:

  • People who just want reprozip shouldn't depend on reprounzip machinery (but code shouldn't be duplicated)
  • reprozip should support multiple operating systems, so it should be possible to install reprozip but switching out the Linux ptracer component
  • reprozip will contain significant OS-agnostic logic, to recognize distro packages and language packages
  • It should be possible to add support for other package managers as additional PyPI packages, though I envision this will mostly be built into reprozip

@remram44
Copy link
Member Author

remram44 commented Jul 1, 2021

Introduced reprozip_core with d27bd1e

@remram44 remram44 self-assigned this Sep 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@remram44 remram44

Labels
T-enhancement Type: En enhancement to existing code, or a new feature T-task Type: Something to be done, neither a bugfix nor an enhancement of the code
Projects
None yet
Milestone
2.0
Development

No branches or pull requests
1 participant
@remram44