Skip to content
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

Add submodule sources #155

Open
vmrob opened this issue Dec 15, 2016 · 1 comment
Open

Add submodule sources #155

vmrob opened this issue Dec 15, 2016 · 1 comment

Comments

@vmrob
Copy link
Contributor

vmrob commented Dec 15, 2016

Currently, the best available method to develop first party dependencies alongside a top-level project is to either use a directory source which currently provides no means to track changes and incurs the overhead of a full clone every build OR manage the dependencies entirely through needy leading to workflow changes for developers and the inability to use normal git tools.

I would propose that needy provide a submodule source that leverages the best of both the directory source and the repository source: management via standard git tools and file/folder modification tracking via git. As an added benefit, I don't think specifying dev mode for submodules will every be necessary which greatly simplifies developer workflow and eliminates a very common user error--leaving a need in dev mode.

libraries:
    mylib:
        submodule: third-party/submodule-dir
@vmrob
Copy link
Contributor Author

vmrob commented Dec 15, 2016

@ccbrown any thoughts on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant