| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2022-09-14 | Add missing `provides` directive | Claudia Pellegrino | |
| Detected by namcap. See also: [1] [1]: https://wiki.archlinux.org/title/VCS_package_guidelines#Guidelines | |||
| 2022-09-14 | Various updates (see full message for details) | Claudia Pellegrino | |
| - Update source URL (project has been moved to PyPA) - Sort dependencies alphabetically - Update `pip-api` comment (package has been updated to 0.0.22) - Remove outdated `python-cachecontrol` comment (package has been updated to 0.12.11) - Add missing `python-rich` dependency - Remove `python-packaging` dependency (declared upstream but already satisfied through `python-pip-requirements-parser`) | |||
| 2022-08-22 | Add missing makedepends | Claudia Pellegrino | |
| 2022-08-22 | Replace `flit` invocation with `build` | Claudia Pellegrino | |
| The `flit` command performs some up-front validation before it actually builds the package. This is intended for upstream project maintainers so they have a chance to learn about issues before they proceed to cut a release. Once a package is released, people who consume the package (which includes package repository maintainers) are assumed to be mainly interested in getting the already-released package to build. Therefore, they may simply want to run the build backend without caring about up-front validation. That’s what the `build` command does: invoke the suitable build backend, which in the case of `flit`, doesn’t run the validation steps. See discussion in [1]. [1]: https://github.com/pypa/flit/issues/580 CC: Thomas Kluyver <thomas@kluyver.me.uk> CC: William Woodruff <william@yossarian.net> | |||
| 2022-08-19 | Bump dependencies; use flit, installer; add LICENSE | Claudia Pellegrino | |
| 2021-12-07 | Bump python-pip-api dependency | Claudia Pellegrino | |
| 2021-11-23 | Update dependencies | Claudia Pellegrino | |
| 2021-11-09 | Initial commit | Claudia Pellegrino | |