option to redirect package installations

[WebFreak001]

trafficstars

I just deleted a fork of a package because that package is now maintained again. I was maintaining it under a different name for a bit because the original owner didn't respond. Is there any option so people who want to install my fork painlesstraits-fork will instead install painlesstraits now or get a warning/error message that they should change to painlesstraits? The fork isn't needed anymore now because of said reasons.

[s-ludwig]

For the most simple forward, you'd have to keep the forked repository around, but change it to target type "none" and instead add a dependency to the original package. You could add some "echo ..." post build command to output a warning message.

But there is nothing built-in - I'm not sure how that could be solved in a general way. The problem is that there are usually complex differences in such a situation, such as independently numbered release versions or incompatible API changes, so that a simple forward wouldn't do the right thing.

[John-Colvin]

A good example of where some cleanup / redirect needs to happen: https://code.dlang.org/packages/containers and https://code.dlang.org/packages/emsi_containers

It's a fairly high-visibility project (involved in people's early experiences wanting to avoid gc, often linked in forums) and the confusion isn't great