Hello.
As we are moving stuff from the mainline to the coastline, I suggest
we finally adopt the HelenOS Coastline as an official project.
Therefore I have created a repository for it:
bzr://bzr.helenos.org/coastline
bzr+http://bzr.helenos.org/coastline
I believe Vojta should have the privilege to import the contents of
his git branch into it.
Thanks, Martin. I will push the changes there as soon as I find some
machine where bzr fast-import works ;-). If you wish to do it yourself,
I certainly do not object.
Is there any practical reason why it needs to be in a separate source
code repository? Why can't it be in the mainline repository?
Perhaps not a practical reason, but it helps to keep the mainline clean
of any ported code. Making the HelenOS code a first-class citizen, a
distinction between ours and theirs. We can enforce different standards
on the two bases (cstyles, optimization options, warning levels, licesnes).
I agree.
On the other hand, it would be practical, to have coastline matrix
rebuilt every time there is a push to mainline, to see whether somthing
broke.
Sure. Once Vojta pushes his code to the official repo, I can write and
debug some hooks for that.
That would be great. Just a sidenote: the rebuilding can take about 8
hours if you rebuild everything for all architectures. And the packages
are about 500MB in size (and require a few GBs during the build).
A follow-up suggestion: how about employing some continous-integeration
software to run also tools/check.sh and once we integrate Martin's
testing framework those tests as well?
Finally, should not be libposix moved to coastline as well? It has only
a very limited reason to exist without it.
Coastline was meant to be a repository for scripts for building someone
else's code. libposix is our code.
Furthermore, libposix heavily depends on libc and, perhaps
unfortunately, libc also has to be aware (to very little degree) that
libposix exist. If we would have more similar libraries implementing a
legacy API (e.g. a ncurses layer about our code or our libx11), then it
would probably make sense to have a separate repository for them.
Because of this, I would prefer to keep libposix where it is.
- Vojta
_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/listinfo/helenos-devel
