Regarding github CI

[Jason Liu]

I believe you are talking about automatically updating Portfiles? I feel
like this has the potential to be incredibly dangerous. As someone who
works on ports that often have a very large number of dependencies, I have
sometimes encountered situations where if the dependencies get updated too
far beyond what the port can accept, then the port ends up broken until the
upstream devs update their code to use the new version of the dependency.

If MacPorts had the ability to have ports be dependent on specific versions
of a dependency like Apt does on Debian, then I might be more inclined to
accept such an idea, but MacPorts basically only has one version of a port
available at any given time.

-- 
Jason Liu


On Wed, Sep 6, 2023 at 5:02 PM Kirill A. Korinsky via macports-dev <
macports-dev at lists.macports.org> wrote:

> Folks,
>
> As you may have noticed a few weeks ago, I opened a PR
> https://github.com/macports/macports-ports/pull/20092 in which I propose
> enabling the execution of port test as part of GitHub's CI.
>
> I understand that not all ports currently have tests, but a lot of them
> does.
>
> My goal here is to enhance the quality of tests for the ports, which will
> allow me to proceed with a bot that runs `port livecheck...` and detects
> when ports are updated. Subsequently, it will open a PR to update a port
> with the updated version and checksums, but only if such a port has tests.
>
> Why? To automate the process of updating ports. We have a vast number of
> ports, and many of them can be updated quite easily. Enabling the execution
> of port tests on GitHub will ensure that such automatically generated PRs
> are of sufficient quality to be merged.
>
> What's the ultimate goal? To keep MacPorts dynamically updated.
>
> --
> wbr, Kirill
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20230906/07e7561b/attachment.htm>