There's another related issue I stumbled upon while playing around with this fix: dependencies.

Say that we have package A depending on B. Both A and B are packages residing in local directories on the system, rather than in remote repositories. So doing:

{
    "name": "script A",
    ...
    "dependencies": {
       "local_dependency_package_B": "master"
    }
}

So how would you specify local_dependency_package_B which would be a path in this case?

There's another related issue I stumbled upon while playing around with this fix: dependencies.

Say that we have package A depending on B. Both A and B are packages residing in local directories on the system, rather than in remote repositories. So doing:

{
    "name": "script A",
    ...
    "dependencies": {
       "local_dependency_package_B": "master"
    }
}

So how would you specify local_dependency_package_B which would be a path in this case?

We could address this by allowing the branch or version in a dependency to also include a file: protocol to indicate a local file path

Firstly, this feature request isn't really related to this MR. This MR is for specifying a local project for the utility at the command line, while this feature request is for specifying in a project file. If this goes any further, turn this conversation into an issue, let's not start tacking feature requests on merge requests...

So I think I'm missing something here in this thought process. A dependency in this situation has to do with defining the source location for installation of required projects of a specific project. You'd not only be installing a list of specified dependency projects, but specified versions of those projects. The way this is being discussed is more like defining how to link projects. That's more of a feature of repositories not projects. In other package management software, you'd update the managers listing of source repositories to include a new local repository.

Repository management is a feature I was working at building out. The BPKG site listing and search is now setup to handle pointing to non-GitHub project repositories. My next feature to add to the utility was the revamp of source handling. This feature is just a natural consequence of that concept. Add a local repository override, that will reduce any resulting complexity.

However, let's stop discussing this feature request on this MR. If we must continue this discussion, create a new issue and link this MR discussion for reference.

Thank you,

Sam

I have been super busy I am sorry! I will get back to this very soon