Repository navigation
Replies: 2 comments 3 replies
|
From reading current What changes. Only the path: Costs
Where it's actually better
Migrating existing publishes
|
|
multi-dist was mainly introduced to fix race conditions, and it is not default to not break existing installations. I would also recommend to set it to true for most use cases. The docs mentioned are outdated since the are not automatically created from the command definitions.. something to improve... |
Uh oh!
There was an error while loading. Please reload this page.
I only recently read #1292 (didn't see the option in the docs)
Seems ideal, cause now I can move my 'pool per dist' mirrors (e.g. gitlab, docker) to a single prefix with all the dists:
Recently had to incorporate ESM/infra-legacy mirrors from ubuntu. Which I wanted to put in our
/ubuntuprefix alongside the regular dists.Gave me a small issue for the pool files (legacy and ESM have their own pools, combining them leaves 1 package)
So then I figured to just use
-multi-distas well, problem solved.And at that point, what's the harm of doing it for every dist in the prefix, or just set it as the default way to publish?
The pull request mentions:
So, two years later, is there any drawback?
More redundant hardlinks? cleanup complications?
I'm not seeing any significant drawbacks other than retroactively doing this leaving some messy pools with the original component folders still in /pool.
All reactions