I think the package name system is case-insensitive (??) but 
case-preserving (definitely), and certainly objects to trying to create two 
packages that differ only in case.

So renaming from FOO to foo won't work, because it considers this an 
attempt to overwrite an existing package. I think. We could probably change 

But here's a trick: try renaming FOO to FOO-x, and then to foo. That might 

On Friday, June 5, 2020 at 5:59:03 AM UTC+2, Siddhartha Kasivajhula wrote:
> ...@Alexis King <javascript:> , let's say I add the new package with the 
> lowercase name but other metadata identical to the old one, including the 
> github repo and the collection name. I would then update everything I care 
> about to use the new package and then wait for a day or two for the docs to 
> show up. At that point, how would the documentation server handle the fact 
> that two packages provide identical top-level collections? Would that be 
> OK? Not sure if it matters that this is a top-level collection name.
> On Thu, Jun 4, 2020 at 8:32 PM Siddhartha Kasivajhula <skas...@gmail.com 
> <javascript:>> wrote:
>> OK, that's a good idea. I guess that still means it would lose the 
>> metadata, correct? That seems less than ideal, but I suppose it's more of 
>> an aesthetic concern.
>> Re: the broader case-sensitivity consideration, for anyone interested in 
>> additional context, it looks like the python package index is case 
>> insensitive 
>> <https://stackoverflow.com/questions/26503509/is-pypi-case-sensitive>, 
>> while Ruby gems are case sensitive 
>> <https://guides.rubygems.org/name-your-gem/>, although it looks like 
>> capital letters are now disallowed 
>> <https://github.com/rubygems/rubygems.org/pull/481> following 
>> discussions including this one 
>> <https://github.com/rubygems/rubygems.org/issues/378>.
>> On Thu, Jun 4, 2020 at 7:41 PM Alexis King <lexi....@gmail.com 
>> <javascript:>> wrote:
>>> On Jun 4, 2020, at 21:23, Siddhartha Kasivajhula <skas...@gmail.com 
>>> <javascript:>> wrote:
>>> I'd prefer to avoid that since (1) it would lose the package metadata 
>>> and (2) it could be off the package index for up to a day (the package 
>>> index refresh cycle) during which time other packages depending on it would 
>>> be broken
>>> This isn’t quite right: it’s true that the pkg-build service only runs 
>>> once every 24 hours, but the only thing that depends on that is built 
>>> documentation. The actual package index is refreshed much more rapidly—on 
>>> the order of minutes. You wouldn’t have to wait very long at all to update 
>>> other packages.
>>> But even if you did, it wouldn’t matter, because there’s an easier 
>>> solution: add your package under the new name *before* you delete the 
>>> old name. Then you can delete the old name once you’ve ensured that 
>>> everything you care about is updated. It’s perhaps a bit strange to have 
>>> the same package simultaneously indexed under two different names, but it 
>>> shouldn’t cause any trouble.
>>> Alexis

You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Reply via email to