←back to thread

202 points sebg | 2 comments | | HN request time: 0.611s | source
1. kazinator ◴[] No.45309209[source]
> But… CRAN had also rerun the tests for all packages that depend on mine, even if they don’t belong to me!

When you propose a change to something that other things depend on, it makes sense to test those dependents for a regression; this is not earth shattering.

If you want to change something which breaks them, you have to then do it in a different way. First provide a new way of doing something. Then get all the dependencies that use the old way to migrate to the new way. Then when the dependents are no longer relying on the old way, you can push out a change which removes it.

replies(1): >>45311957 #
2. constantcrying ◴[] No.45311957[source]
>If you want to change something which breaks them, you have to then do it in a different way.

Almost every other package repo works differently and publishing packages which would break other packages is more than common, it is the standards way to publish updates.

>Then get all the dependencies that use the old way to migrate to the new way. Then when the dependents are no longer relying on the old way, you can push out a change which removes it.

This is actually how no software repo works as it is actually insane.