Rename curve ports to include a namespace within their port names

[SunBlack]

• Changes comply with the maintainer guide.
• SHA512s are updated for each updated download.
• The "supports" clause reflects platforms that may be fixed by this new version, or no changes were necessary.
• Any fixed CI baseline and CI feature baseline entries are removed from that file, or no entries needed to be changed.
• All patch files in the port are applied and succeed.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Exactly one version is added in each modified versions file.

Solves #49096

[BillyONeal]

@Curve @MehdiChinoune @yurybura @mutptr Tagging you because you have edited one of these in the past. Given that several of these have likely to conflict names and the set is only growing over time I think @SunBlack makes a good point but I would like to give folks who might care a chance to chime in.

There's also no requirement that we necessarily have to rename any of the existing ones; the names are already effectively "given away" so we could say to only do this for anything added. But @Curve et al. may appreciate all their libraries sorting together.

[MehdiChinoune]

No, I didn't touch any of them in the past.

[BillyONeal]

No, I didn't touch any of them in the past.

I tagged you due to #30368

[BillyONeal]

I see now: saucer is implicated but is just a customer itself. Sorry for the extra ping :)

[Curve]

@Curve @MehdiChinoune @yurybura @mutptr Tagging you because you have edited one of these in the past. Given that several of these have likely to conflict names and the set is only growing over time I think @SunBlack makes a good point but I would like to give folks who might care a chance to chime in.

There's also no requirement that we necessarily have to rename any of the existing ones; the names are already effectively "given away" so we could say to only do this for anything added. But @Curve et al. may appreciate all their libraries sorting together.

I think this makes sense - my libraries often have single word names that could conflict with others.

Out of curiosity: Is this the first instance of using namespaces for the ports? If so, I think this is actually a good idea in general :)

[yurybura]

I think @SunBlack makes a good point but I would like to give folks who might care a chance to chime in.

It's a very good idea to make names more unique and avoid name conflicts.

[BillyONeal]

Please just deindex these rather than leaving empty ports.

[SunBlack]

So there's no more transition period where the old port redirects to the new one (and yes, I forgot to set up the redirect)?

[BillyONeal]

I think what we have found over time is that those redirects end up counterproductive. Now that we made sure it doesn't break folks using manifest mode we have been much more willing to just deindex stuff.

[SunBlack]

Good to know that the behavior with old ports has now changed 👍

[dg0yt]

Out of curiosity: Is this the first instance of using namespaces for the ports? If so, I think this is actually a good idea in general :)

@Curve There is a "Use distinctive port names" guideline:
https://learn.microsoft.com/en-us/vcpkg/contributing/maintainer-guide#check-names-against-other-repositories

[SunBlack]

Anyone seeing the reason, why the CI want to readd the removed ports (see summary).

[BillyONeal]

Anyone seeing the reason, why the CI want to readd the removed ports (see summary).

I did touch that recently... maybe there's another bug. Let's see if merging fixes it

[BillyONeal]

:sigh: This is what I get for touching ANYTHING

[BillyONeal]

Sorry, juggling too many balls at once and accidentally pushed to the wrong thing

[BillyONeal]

OK, this should be fixed in #51431. If build results come back OK except for that check I will merge through it. (Sorry for touching this PR; I did not mean to)

[BillyONeal]

Thanks!

[BillyONeal]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).