On 27/04/15 10:12, Andrew Stuart wrote:
It would be generally more easy to understand how everything fits together if
there was only one project repository with everything in it.
Can you be more specific on how having only one repository would help?
While there is some synergy between various repos, everything does not
require everything, and a grand unification would, at least for me,
imply two regressions:
1) lack of ability to give finer-grained push access
2) everyone is forced to checkout everything, regardless of whether it
is required for their use case or not
As a workaround, you can clone all subrepos under a single directory ;)
While I do agree that it can be difficult for a newcomer to see how
everything fits together, I think the problem is lack of a few
paragraphs of high-level documentation, not the repo structure. I see
two contributing factors to confusion: 1) rump kernels have use cases
beyond just the unikernel 2) nobody yet really knows what unikernels
should be like, so there's no frame of reference for users/developers
like you'd have when running software on $unix. I think we're slowly
moving in the right direction, though, and every "hey that's not
understandable" cry helps us zero in on the target.
