Welcome to mirror list, hosted at ThFree Co, Russian Federation.

cygwin.com/git/cygwin-apps/calm.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2024-01-04Factor out writing the details in the package summary pageJon Turney
Contain the details in a table of class 'pkgdetails' for more layout control.
2022-11-26Change x86/ to x86_64/ in test dataJon Turney
2020-08-23Include a date in package summary pageJon Turney
Include build date (strictly, the package archive mtime) in the package summary HTML page. Also refine package size units to KiB, since that's what we actually use. Use a fixed timestamp (in UTC) for all packages in test data.
2020-05-25Remove support for curr: appearing in override.hintJon Turney
This doesn't really work the way it's expected to across setup versions, and isn't a good way of approaching the problem (current alternatives: make the version you want to be preferred have the highest non-test version, or use replace-versions: to cause higher versions to be uninstalled). Future work: lots of cruft for handling stability level overrides remains, which can all be cleaned up.
2019-07-04Create a separate package object for the source packageJon Turney
Create separate package objects for the binary and source packages. This is generally a simplification to the data model. One slight wrinkle is that stale file detection needs to be aware that .hint files may now be used by both a binary and source packages, and so should only be removed if both packages are stale. (Since the source package cannot be stale if the binary package isn't, we solve this by making the source package control the staleness of the hint, in that case [except for archives which are sourceless for permitted reasons, which we now explicitly annotate as such]). 'external-source' is now always followed, rather than checking for the source for a given version in the current package first. This exposes a handful of (migrated) hints which contain an unnecessary external-source. Write separate package summary pages for source packages Always create binary packages when uploading to allow replacement hints, otherwise, only create a package if there's archives for it to contain to avoid creating empty packages from the relarea. Note: since we don't put source packages into a separate namespace, there is a potential collision if both 'foo' (source package 'foo-src'), and 'foo-src' (source package 'foo-src-src') exist. That would be daft, and there aren't currently any examples of this. Forbid package names ending in '-src' to avoid such problems.
2019-06-20Omit maintainer in package summary page if we don't have any detailsJon Turney
Also improve the package/maintainer validation we do, to better detect non-obsolete, maintainer-less packages. Also make some unnecessarily absolute URLs relative.
2019-06-20Round file size up in package summaryJon Turney
Round the file size up in package summary (so tiny, but non-empty packages are reported as 1kB, while empty packages are still reported as 0kB)
2019-06-11Use summary/description rather than sdesc/ldesc in package summary pageJon Turney
Also HTML escape those texts
2019-05-27Show test status for versions in package summary pageJon Turney
2019-05-27Add navigation frame to package summary pageJon Turney
Add navigation frame to package summary page Set execute permission required for SSI
2019-05-27Generate a per-package summary HTML pageJon Turney