I've almost completed rebuilding the compiler suite (C, perl) for the debian.5.0 platforms, but we have to resolve the following problem before we can move forward.
Jerry's boot.efs setup was used to build all the initialize binaries, but Jerry currently only has the rhel.5 platforms. David's boot.efs setup was used to build the new debian.5.0 binaries, since we have both rhel.5 and debian.5.0 platforms. I can upload the new builds, but now we really can't build new releases for those projects in Jerry's setup, because doing so will NOT produce the debian.5.0 binaries. It is not practical to download/port/re-upload everything Jerry builds over in David's setup, as an ongoing means of supporting that platform. The code's simply not designed for that and won't scale well. There's nothing preventing two different domains from both creating the next buildXXX for a given release, and colliding. The model I can support going forward is that any given metaproj is "owned" by ONE domain. We need to address the multiple boot.efs domains we've created, since this works fine for testing the bootstrap process (not that anyone but me has tried it yet), but we're really using these installations more like a "real" EFS domain. Right now, the debian.5.0 compiler builds are sitting on David's machines, and as soon as I upload them, it greatly complicates how we build and share infrastructure going forward. I think we need to establish a "home domain", where we do ALL of the content build and uploading, for a given metaproj. This is really more along the lines of the model we've discussed in the past, where a metaproj is owned by a given domain, and that domain is responsible for all uploads for that metaproj. Everyone else downloads, or they can compile things on their own, locally. The current setup we're using breaks this model, since we have 3 independent boot.efs domains (and to make matters confusing, they LOOK like they are all part of the same domain, but they really aren't). This might be a good time to start talking about a real openefs.org domain, using publicly visible machines, with real hostnames, etc. The bottom line is that we can not merge the debian work with the content on openefs.org until we resolve how we're going to manage this going forward.
_______________________________________________ EFS-dev mailing list [email protected] http://mailman.openefs.org/mailman/listinfo/efs-dev
