Have boulder+moss autoindex local binary collections prior to each run?

ermo

For convenience, it might make sense to have both boulder and moss autoindex available local binary collections prior to each run.

There could be an optional flag (say, --noindex) which turns off this behaviour for each tool.

Assumptions:

By default, boulder will upon successful builds copy newly built .stones to the local binary collection directory specified with -p (e.g. -p local-x86_64) unless --nocopy is specified.

This would have the following benefits:

Upon each new boulder build -p local-x86_64 invocation on a local system, the binary .stones already present in /var/cache/boulder/collections/local-x86_64/ will automatically be available for boulder.
Upon each new moss install or moss update invocation, files already in /var/cache/boulder/collections/local-x86_64/ will automatically be used to satisfy dependencies if the local-x86_64 collection is enabled.

As I see it, this has the benefit of creating a link between the action (cp *.stone /var/cache/boulder/collections/local-x86_64/) and the intent ("have the .stones currently in /var/cache/boulder/collections/local-x86_64/ be available for installation by default").

Suggested abbreviations for easier writing:

binary collection -> bcol
source collection -> scol

Ikey

With @joebonrichie's PR now merged, we now automatically reindex on configuration of remotes within the build environment. Next up is promotion of assets to that local collection.

Opinion: Need "winner" for multiple-local-collection scenario, go with the highest?

ermo

Ikey Opinion: Need "winner" for multiple-local-collection scenario, go with the highest?

Yes, it's the simplest and most intuitive option.

This, however, means that we need a way to distinguish at a glance which local collection has the highest priority -- i.e. default ordering with highest number at top of list, assuming that no two collections can have the same priority?

Think of a stack that show the collection with the highest repository at the top; you see the stuff on top "first".

Example:

What I would like to see to see:

moss -D sosroot/ lr
volatile    [active] https://dev.serpentos.com/volatile/x86_64/stone.index    Priority: 10 Comment: User added repository
protosnek   [active] https://dev.serpentos.com/protosnek/x86_64/stone.index   Priority: 0 Comment: User added repository

What I'm currently seeing:

moss -D sosroot/ lr
protosnek   [active] https://dev.serpentos.com/protosnek/x86_64/stone.index   Priority: 0 Comment: User added repository
volatile    [active] https://dev.serpentos.com/volatile/x86_64/stone.index    Priority: 10 Comment: User added repository