summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/rangehttpserver
diff options
context:
space:
mode:
authorJason Yundt <jason@jasonyundt.email>2024-11-12 09:49:00 -0500
committerJason Yundt <jason@jasonyundt.email>2024-11-14 19:30:22 -0500
commit58542c2d7eee26541aba35745e2eec40a0ee22b6 (patch)
tree22b270a922fecfb16f586d44cce6c68158cf9f90 /pkgs/development/python-modules/rangehttpserver
parent4aad3e8c772be76cbbc6fd2530204bf6ff993d1b (diff)
descent3-unwrapped: init at 1.5.0-beta-unstable-2024-10-29
Originally, I had thought that the version number should be 1.5.0-unstable-2024-10-29. It ended up being 1.5.0-beta-unstable-2024-10-29 due to a technicality. The package versioning conventions in pkgs/README.md say: > - If a package is a commit from a repository without a version > assigned, then the `version` attribute _should_ be the latest upstream > version preceding that commit, followed by `-unstable-` and the date > of the (fetched) commit. The key phrase here is “preceding that commit”. The commit for Descent 3 version 1.5.0 was created in a separate branch [1]. That being said, there was a beta version of 1.5.0 that was released in 2005 [2]. That beta version of 1.5.0 was indeed merged into Descent 3’s main branch [3], so it’s the latest upstream version preceding the fetched commit. [1]: <https://github.com/DescentDevelopers/Descent3/commit/0388d0758298d6e474ddda266062a96d76493c44> [2]: <http://descent3.com/downloads.php> [3]: <https://github.com/DescentDevelopers/Descent3/commit/df209742fcda59d466b849eff9ee0e7b908d7d40#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5>
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions