You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When developing and testing packages, they are not saved in github but instead are in the local machine of the developer, machu picchu needs a way to link to those versions of the packages.
Peru has peru sync [package] [directory]
In Cargo a path option is added to the dependency. It currently has no way of not modifying the cargo file so it has to be reverted manually before pushing
npm has a link command that when run without arguments, creates a package link in the current machine, and when run in another project, npm link [package] creates a symlink to the previously linked package as the dependency
I like the idea of a manifest.patch.scl file that is untracked by git that overrides the manifest file, along with an option for an mp package to point to a directory rather than a git link.
The text was updated successfully, but these errors were encountered:
naturallymitchell
changed the title
A way to link mp to local packages
support packages sourced from local filesystem, not just remote urls
Feb 24, 2019
When developing and testing packages, they are not saved in github but instead are in the local machine of the developer, machu picchu needs a way to link to those versions of the packages.
peru sync [package] [directory]
npm link [package]
creates a symlink to the previously linked package as the dependencyI like the idea of a
manifest.patch.scl
file that is untracked by git that overrides the manifest file, along with an option for an mp package to point to a directory rather than a git link.The text was updated successfully, but these errors were encountered: