dub-registry icon indicating copy to clipboard operation
dub-registry copied to clipboard

A way to change package names

Open p0nce opened this issue 11 years ago • 4 comments

We'd like to change the "derelict_extras-opencl" package to just "derelict-cl". But if we do, people relying on the older name will have a broken build. A way to solve this problem would be nice, though not an absolute requirement.

p0nce avatar Dec 08 '14 12:12 p0nce

Yeah sounds reasonable, the registry should keep the old name reserved and do a redirect. Will also need a dub update to understand the redirect and print "please rename your dependency" message. For the time being you can probably register the package a 2nd time under the new name.

MartinNowak avatar Dec 08 '14 12:12 MartinNowak

For the time being you can probably register the package a 2nd time under the new name.

I did that for similar cases in the past. This time we transferred Github ownership instead of creating a new repo, and took the obvious name. So recreating again would conflict with existing Github URL. Unless we transfert ownership backwards which is a way out.

p0nce avatar Dec 08 '14 13:12 p0nce

This time we transferred Github ownership instead of creating a new repo, and took the obvious name. So recreating again would conflict with existing Github URL. Unless we transfert ownership backwards which is a way out.

I didn't got that, what's the problem?

MartinNowak avatar Dec 08 '14 15:12 MartinNowak

I'm running into this as well. I renamed the TSV Utilities repository from eBay/tsv-utils-dlang to eBay/tsv-utils. Everything smooth so far, except that the DUB Registry won't allow the package to be renamed. It also won't update the project after the tagging the repo. The errors given are because the name on the project conflicts with the name in the updated dub.json file. (I updated the dub.json files with the new repo name as part of renaming it.)

For now I'll create a 2nd project with the new name.

jondegenhardt avatar Jul 16 '18 02:07 jondegenhardt