I'm here to discuss a relative common scenarios I have found.

Many people host in the same repo (links below) multiple tools (micro-tools), I thinks, to avoid to have a large amount of repetions of the same git repo into the various phases of publish a new package on the registry.

Having something to act as package collector for multi-tools repo is in my mind, but not clearly how land on this.

Just for hypothesis

A file in the root of the project called bpkg.json with a special key collection list variuous path as keys and sub-data as value

{
  "collection": {
     "xcat2": {
             "name": "xcat2",
             "path": "bin/xcat2",
            "license": "..."
     },
     "special-split": {
             "name": "special-split",
            "path": "bin/special-split"
            "license": "..."
     }
  }
}

In that case, suppose to use it in this way:

bpkg install orgname/reponame/collectionitemname@0.0.1 -g

In this case who goes under the bpkg name (skip to add orgname in the package)

Benefits

• Tool-maintaner can host all of your code in one place avoid fragmentation. Instead tool user, can install the only needs and not the entiere list of tools
• Single micro-tool can have independent page on the registry separated to the collection page, in this case focus on tool is good instead of focus to install a non-homogeneous repo of micro-tools

Links

• https://github.com/oldratlee/useful-scripts/tree/dev-2.x/bin
• https://github.com/mertcangokgoz/UsefulBashScripts/tree/master/Scripts

@jwerle @Potherca @samlikins does that make sense for us?