Update PURLDB with all ABCTK releases

Abierto
  • ¿Algo no está bien?
#582 2 comentarios 0 reacciones 3 asignados Ver en GitHub

@pombredanne ya está trabajando en esto.

Desde el 15/3/2025.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Important needs design

We need an automated process to update PURLDB whenever we release a new version of any AboutCode.org package - we should start with aboutcode-toolkit. If we have each release in PURLDB then you should be able to get that data for a Product in DejaCode with the Improve Packages from PURLDB Action.
The steps seem to be:

  • Use the PURLDB API to get the current list of PURLs for aboutcode-toolkit and their data
  • Identify missing or incorrect data in the existing PURL data and correct it
  • Identify the missing PURLs and add them to PURLDB
  • Figure out how to automatically populate the PURLDB for each new release of aboutcode-toolkit

This is a pilot for a process to:

  • Clean up existing PURLDB data for all AboutCode projects
  • Automate adding PURLDB data for each new release of an AboutCode project
    The initial focus should be on AboutCode projects that are published to PyPI to keep this simple.

An open question is how to handle the different types of packages that we usually publish for aboutcode-toolkit (and most other AboutCode projects). Using v11.0.0 AboutCode Toolkit v11.0.0 as an example, we have 4 downloads:

  • aboutcode_toolkit-11.0.0-py3-none-any.whl
  • aboutcode_toolkit-11.0.0.tar.gz
  • v11.0.0.zip (Source Code)
  • v11.0.0.tar.gz (Source Code)

For patch releases like AboutCode Toolkit v11.0.1 and v11.0.2 (and many older versions) we only release the source packages.
Since each PURLDB record has one Download URL we will need some way to record the four different PURLs.
This seems to call for a qualifier so that the records will be unique. My guess is that we might want to treat the wheel as primary in the PyPI context and perhaps not use a qualifier for it.

Lenguaje dominante
Python
Estrellas
100
Forks
48
Sin PR fusionados en 30 d

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de aboutcode-org/aboutcode-toolkit

Todos los issues de aboutcode-org/aboutcode-toolkit

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.