starpath.0.1.2 is 404

[Kakadu]

@mtoohey31 was it intentional?

  - [starpath.0.1.2] https://github.com/mtoohey31/starpath/archive/refs/tags/0.1.2.tar.gz (code
    404 while downloading https://github.com/mtoohey31/starpath/archive/refs/tags/0.1.2.tar.gz)

[mtoohey31]

Whoops my bad, I'm moving my stuff off GitHub; I was trying to leave the stuff that people might be depending on though but I forgot about this one. It should be back now.

[Kakadu]

Nice!
@mtoohey31 do you plan to change links to non-Github repo in a nearest future?

[mtoohey31]

If there's a way for me to migrate things without breaking existing projects then I'd be interested in doing that. I'm not too familiar with opam though. I assume I would re-create the non-GitHub repository, then update opam to point to the new link while still having the GitHub version around?

I guess the main thing I'm wondering is whether the expectation is that links that were previously in opam should remain valid, or if it would eventually be ok to remove the GitHub version after performing the steps above and waiting a bit.

[shonfeder]

I assume I would re-create the non-GitHub repository, then update opam to point to the new link while still having the GitHub version around?

I guess the main thing I'm wondering is whether the expectation is that links that were previously in opam should remain valid, or if it would eventually be ok to remove the GitHub version after performing the steps above and waiting a bit.

URLs can change on packages, so long as the sources remain identical (as measured by the source integrity hashes), so no problem there. Once the package data is updated, there is no need to maintain the old URLs. It is true that older commits of the repo will point to broken URL's, but AFAIK, this happens and is not a problem.