Eh, sorry. My original version of this had the slug first then the name, but then I realized that a lot of the slug choices don't work for that since the slug directory is top-level, so I changed the ordering, which works for exact name collisions but not for inexact case collisions—which version of the name to you choose? For case collisions, you want the slug first and the name after so that each one can have it's own folder. Alternately: don't use a / between the two and do A/APackage.$slug/ instead since then each can have its own capitalization.

More musing:

Re "number based on the ordering of UUIDs" option, we probably don't want the same directory to potentially change which package is held in it. It would be much better if adding a new package can move an existing package but not lead to a new package being in the same place.
The whole UUID option I think takes up too much path length—older Windows versions really do not like long paths; newer ones are fine with it, but there are still tools that get upset. But maybe this is ok, after all we control the tooling that will access these files and we'd like to switch to not unpacking the registry at all, especially on Windows for just these kinds of reasons.
A fixed number of UUID bytes still has the potential for collisions.
The slug computation has the same issue although collisions are quite unlikely—but unfortunately much less so on a case insensitive file system! In that case there are 36^5 unique slug values and the probability of collision on the order of one in sqrt(36^5) = 7776 which is not nearly safe enough for my taste. It's actually worse than that because we're choosing between case-distinguishable slugs uniformly, but case-indistinguishable ones non-uniformly, so it may be about 1/5000 chance of collision on a case-insensitive file system.

That only leaves two viable options:

All of the UUID (despite concerns about path length)
Enough of the UUID to be unique. I would suggest using 8 digits as a minimum (1/65k chance of collision) but adding more of the UUID if necessary to avoid a collision.

If we went with the second option, the total path would be A/APackage.$(string(uuid)[1:n])/ where n is chosen to be enough of the UUID to be unique and at least 8.

Folder cases #37

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions