[haiku-development] Re: Open Discussion
- From: Adrien Destugues <pulkomandy@xxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 12 Mar 2017 11:25:16 +0100
On Sun, Mar 12, 2017 at 10:33:32AM +0100, Ralf Schülke wrote:
Hello developer,
This is not a cretan, it is a note of understanding.
My occasion is the outsourcing of haiku components in haikuporter, such as
bash, truetype and other.
Would not it be better to bring these things back to haiku back in order to
have a base os with all the components.
No. It is too much work. When we did that, we had to rewrite the build
system for all these things using jam, which led to countless bugs
because their configure scripts wouldn't be run, and made it a nightmare
to keep things up to date.
It also pollutes the result of tools like Coverity scan (most of the
results we get from that are error in 3rd party code, not ours).
So there is a difference to things that are important in base and to build
base os and these things should be in a source tree, so a transparent
overview, so you need only haiku git clones and can build immediately,
without the in haikuport Things.
You can do this already, it downloads pre-built packages for the
dependencies. If you think the binaries are not reliable, then how can
you think the git sources are reliable. And do you really think you can
audit the sources to check we (or some malicious people who somehow
compromised our servers) didn't hide something in there too?
There should be a way to build all the packages from sources, instead of
downloading binaries, for people who really want to be sure what they
build. However, the solution for that is definitely not "let's put
everything in a single git repo". It could be haikuports-cross and
bootstrap builds. However, we never really got that working and no one
has stepped up to maintain the feature working. It seems no one cares
enough in the Haiku community. Patches welcome!
--
Adrien.
Other related posts:
