[haiku-development] Hosting non-x86 images at Haiku-Files ?

  • From: Matt Madia <mattmadia@xxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Wed, 28 Oct 2009 14:58:00 -0400

greetings all,

What is everyone's thoughts about hosting non-x86 images at Haiku-Files?

There's a few reasons I'm asking...

Even though those platforms are no where near the level of x86
functionality, they are still a valuable resource for people who are
interested in the ports -- either for testing the images, to simply
check the status once in a while, or what-not.
There's also a certain "ooh, aaah, shiny" aspect of having those ports
visible. :)

But more importantly, the current trademarks policy/distro guidelines
is fuzzy at best about 3rd parties hosting non-official self-built
images.

Since the build system allows for variation, there could be
differences in what a 3rd party provides and what is provided
officially.  Eg, not enabling --use-xattr on a proper filesystem
*could* lead to unexpected issues. The various  "--include-*" options,
as well as any stray items in UserBuildConfig could also lead to
end-product differences.

Currently, my Build-O-Matic machine is tracking X86 & PPC.
Arm, m68k, and mipsel are not tracked at this point.  m68k requires
too many local modifications, arm required a custom build command (i'm
working on fixing this in a new rewrite --
http://dev.osdrawer.net/projects/haikubuildomatic/repository/show/branches/rewrite2),
and mipsel --- well, i cannot recall exactly why it is not tracked.
So basically, PPC and eventually Arm could be built automatically.

For uploading the non-x86 images and the frequency, I'm open to suggestions.
 * Maybe a cron script for bi-weekly/monthly uploading
 * Giving trusted people who are interested in those ports, ssh access
to my BOm machine to manually trigger and upload
* ...?


--mmadia

Other related posts: