-
Notifications
You must be signed in to change notification settings - Fork 96
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
Extends bpkg compatible packages #100
Comments
There's a discussion answering this question here: #17 I'd also like to have |
Thank's for that informations. |
I honestly don't know... @jwerle is the most active but I'm guessing he doesn't have much time to spend on this project. I'd say things are still active, if somewhat delayed. |
@mbl-35 yes it sure is. I'm happy to send invites for those interested in actively driving this project forward. I'm pretty occupied these days, but still very happy to participate in the conversation! |
It would be great if the install et getdeps process could be extended to find a bpkg repo.
I mean, not only to search about a package.json or Makefile, but also a bpkg.json metadata file decription file (set before searching for package.json).
This is actually the only restriction (with @hydra1983 new features for gitlab target) why I can't use bpkg in a project (with composer and npm...).
I cant use npm and bpkg on a same project...
What was the reasons to have packages.json name (used by npm) ?
The text was updated successfully, but these errors were encountered: