I've spent recently quite a lot of time trying to get installable repos
installed as droplets.
The problem that I will inevitably face is the conflict and ordering
between dropins and droplets, and possibly other mechanisms, like
profile dropping, etc.
I was thinking about refactoring dropins to have:
(a) central service for processing startup installation changes
(b) service definition for installation changing services
(c) implementation of dropins service.
a. would be responsible for getting a request, repositories, caching
them and executing request/plans
c. would scan the dropins folder, produce a request and pass it to a.
The point is that I'd like to avoid multiple refreshes of framework and
solve in some way obvious startup conflicts (what is first? dropins or
Do you think something like this could make into official p2?