Feature review: Customizable repo name on initial clone to keep path lengths short

[abdurraheemali]

Apparently some repos are so large that when using scalar to enlist, the three extra characters from <repo> to <repo>/src causes errors since they don't handle path names larger than 16 characters too well and that pushes them over the limit for some files that were at the edge before with just <repo>.

Do we want to permit an option to rename the resulting directory after scalar clone from
<repo>/src
to something like
<custom>/src
where <custom> is shorter than <repo>?

Would that be an antipattern?

https://docs.bazel.build/versions/5.0.0/windows.html#best-practices This is how Bazel gets around path limitations. If customizable naming is a no-no, could fsutil 8dot3name set 0 help? Would that be in git for windows or upstream of it?

https://o365exchange.visualstudio.com/O365%20Core/_git/ControlPlane this is one of the repos I'm talking about: having an /src doesn't really make sense here since there's already a /sources and a /build path (making the argument from the FAQ not apply as clearly here). So for the source code we're going to <repo>/src/sources which is a little silly.

What do you guys think?

[abdurraheemali]

You can specify the name before the "src". You can run "scalar clone r" to put it into "r/src".

The "src" directory is less critical for Scalar than it is for VFS for Git, so it could potentially change behind a command-line option.