Decide a consistent URL for Python sources
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 141
- Forks
- 146
- Avg merge
- 11h 7m
- Merged PRs (30d)
- 407
Description
There isn’t currently a standard for PyPI source URLs in Solus package builds. AerynOS uses URLs in this format:
https://files.pythonhosted.org/packages/source/p/python-dateutil/python-dateutil-2.8.2.tar.gz
What is the preferred approach for Solus?
If this format is accepted, I’ve prepared a modified version of new-package.sh that automatically sanitizes the source URL to match it. I can also update the Packaging Changes and package.yml documentation accordingly.
Aeryn issue: https://github.com/AerynOS/recipes/issues/11
Contributor guide
No contributing guide indexed for this repository
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 by reviewing the proposed PyPI source URL format and the related AerynOS issue. Then inspect new-package.sh, Packaging Changes, and package.yml documentation to determine the affected changes. Done means Solus has a decided URL standard and the script and documentation consistently reflect it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100