I'm pleased to report that the "rename swap" of Originalname ->
Originalname-x -> originalname worked like a charm :) It also preserved the
metadata. Also, the dependent packages built successfully within about an
hour of the upstream rename. Thank you both for your suggestions and input.
If
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
@Alexis King , 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
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
> On Jun 4, 2020, at 21:23, Siddhartha Kasivajhula 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
A little while ago I uploaded a package to the package index and entered a
Titlecase name for it. I've since learned that this becomes the identifier
for the package that will be used by raco from that point on (as opposed to
being used only on the package description page, as I assumed then). I'd
6 matches
Mail list logo
