Skip to content
This repository has been archived by the owner on Mar 30, 2023. It is now read-only.

Use or delete ZCPKG_PATH_LENGTH_BUDGET #6

Closed
zyrolasting opened this issue Aug 10, 2020 · 0 comments
Closed

Use or delete ZCPKG_PATH_LENGTH_BUDGET #6

zyrolasting opened this issue Aug 10, 2020 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@zyrolasting
Copy link
Owner

zyrolasting commented Aug 10, 2020

ZCPKG_PATH_LENGTH_BUDGET is currently dead, mainly because I wasn't sure how to use it.

I think it makes sense for use in a report where you:

  1. Assume a given workspace directory
  2. Find the longest path in the workspace
  3. Subtract the length of the longest path from the path budget.

So if you say a workspace sits in a Windows C:\Users\John\Code directory, you can estimate if a workspace will create a path that exceeds Windows' default max path length (which is pretty short, and causes issues like microsoft/nodejstools#69).

I hesitate to implement this because it could just as easily be a package written for zcpkg. I'm partial to keeping it lean, but the only defense for putting in this feature is that zcpkg does make this problem possible.

@zyrolasting zyrolasting self-assigned this Aug 10, 2020
@zyrolasting zyrolasting added the enhancement New feature or request label Aug 10, 2020
@zyrolasting zyrolasting changed the title Repurpose ZCPKG_PATH_LENGTH_BUDGET? Repurpose ZCPKG_PATH_LENGTH_BUDGET? Aug 10, 2020
@zyrolasting zyrolasting changed the title Repurpose ZCPKG_PATH_LENGTH_BUDGET? Use or delete ZCPKG_PATH_LENGTH_BUDGET Aug 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant