[haiku-development] Re: Package Building and Beta1

  • From: kallisti5 <kallisti5@xxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Wed, 26 Jul 2017 08:39:55 -0500

On 2017-07-25 17:45, waddlesplash wrote:

On Tue, Jul 25, 2017 at 2:29 PM, Julian Harnath
<julian.harnath@xxxxxxxxxxxxxx> wrote:
The main issue is, and has been for a long time, the automated package
building. Knowledge about what works and what doesn't is a bit...
distributed. So I'd like to ask those, who know about it in detail, to fill
in here with what's missing (e.g. problems that still need to be solved).

Before the latest switch of the package building to Kitchen, Adrien was
putting a lot of work into a release branch of the haikuports repository,
and as far as I understand, the branch is in a stable state that is pretty
much "ready to go".

On the package building end, I hear that Kitchen is ready to go.

Not quite. We still need a reliable GCC2 builder -- arfonzo setup one,
and so did kallisti5, but both have been terribly unreliable in
staying connected at all (as of right now, the x64 builder is online
and has been for quite a while; but the GCC2 ones mysteriously went
offline some time ago.)

My GCC2 builder qemu VM locked up during the builds. A quick restart and
she's back online. The x86_64 package builder has been pretty stable running
on the MacMini.

As part of working towards the release, I created a http and https server for
the package builder artifacts:

https://eu.hpkg.haiku-os.org/
  The idea is, long term we'll have us.hpkg.haiku-os.org, etc.

You can attach to these repos and try them out:

pkgman add-repo https://eu.hpkg.haiku-os.org/haikuports/master/repository/x86_64/current/
pkgman add-repo https://eu.hpkg.haiku-os.org/haikuports/master/repository/x86_gcc2/current/

Keep in mind these repos are experimental and may "break everything"

 -- Alex

Other related posts: