-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SR-159] Add ability to specify localpath for a dependency. #5444
Comments
We agree, and intend to make this less tedious. But in the interest of a healthy packaging ecosystem, any package that is remote will require versions still. |
Comment by Kostiantyn Koval (JIRA)
Agree |
Comment by James Richard (JIRA) Yeah, this would make development significantly easier if you're working on a library-oriented architecture. I would love to see this as soon as possible. |
Sorry, I'll try to do this sooner. I have been waiting on myself because I have been rethinking Package.swift but I can get something in there quicker than that. |
Related to SR-2261 |
And yes, we really would want this, since it's a very natural thing to want to do, especially during bring-up. |
We decided we won't do this, the new branch feature will help during bring up. |
Additional Detail from JIRA
md5: 2e74a9a37d27f5dcd089924474b89238
relates to:
Issue Description:
Use case:
I want to create a simple module on my PC and specify it as a dependency.
Now to make it work i need to create a .git and add a version.
this makes the process of creating new Packages more complex and hard.
The text was updated successfully, but these errors were encountered: