Ability to use Package filenames when publishing
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 71
- Forks
- 91
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 22
Description
We have a bunch of older deb packages that we need to serve that unfortunately have filenames which don't conform to name-version-architecture.deb. Based on my reading of the publishing code, it looks like it always uses this package filename method (see here and here). Which in turn calls this name method that generates the published package's name with name-version-architecture.deb.
It does look like though that when the package gets added to pulp_deb that it stores the original package filename in relative_path. But I don't see an option/way to actually tell pulp_deb to use relative_path when publishing. So two questions: first is it possible today to somehow use relative_path when publishing and if not, how could we support it (maybe a config variable or a publication create parameter)?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in pulp_deb/app/tasks/publishing.py around line 206 and pulp_deb/app/models/content.py around lines 65-69. Trace how relative_path is stored and how the published filename is generated, then determine how publishing could select the original filename. Done should provide a defined way to publish using relative_path, such as a supported option or parameter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100