I'm in the process of rolling the 0.9.8 releases of CI and OpenSSI. In
the interest of stream-rolling _source_ releases, I make the following
two proposals:
1) The _source_ release of OpenSSI will no longer include CI code. CI
will have to be downloaded and built separately. The two were packaged
together in the past because there was no binary releases of OpenSSI. I
wanted to make things as easy as possible for the novice user. These
days we do have binary releases, so I'm much less inclined mash together
the CI and OpenSSI repositories every time I roll an OpenSSI release. Of
course, CI code will continue to be compiled as part of _binary_ OpenSSI
releases.
2) Modified base code in the OpenSSI _source_ release will be
distributed as patches against the base source. I've done this since the
beginning for the kernel code. I'm proposing that I also do this for
util-linux, e2fsprogs, devfsd, and anything else we need to modify. This
will make downloads smaller, since the unmodified base code doesn't need
to be included. The trade-off is that it will be harder to build. To do
this, a user must separately download source for util-linux, e2fsprogs,
etc., manually apply patches against them, and build each according to
its own instructions. Of course, complete RPMs will be provided in
_binary_ OpenSSI releases.
I'm open to debate about these proposals. Let me know what you think,
Brian