[haiku-development] Re: Package Building and Beta1
- From: Adrien Destugues <pulkomandy@xxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 30 Jul 2017 11:18:45 +0200
On Sun, Jul 30, 2017 at 09:22:06AM +0200, Michael Lotz wrote:
How do
release branches factor into this, isn't there going to be just one repo for
the whole beta1 line?
The plan (well, my plan - I'm not sure everyone agrees on that) for beta1 is
that yes, since the API/ABI is frozen there we only need a single repo
for the beta1 line. If a package only runs after a particular bug is
fixed in Haiku, it does not land into the release branch (and repos) until
a beta2 is out (this forces us to release new betas from time to time).
Oh, and one more thing: I noticed that the buildmaster doesn't share
"any" arch packages between arches. This seems to be a major
annoyance, because some of the _data-any packages for games are
500MB+, and there isn't any reason to duplicate them between
architectures. (Seems like this can be solved by symlinking the
"packages" directories of the ports trees together -- and this would
also allow for a single "packages" directory to be served, which is
how the present distribution model works, too.)
Symlinking would probably work for this, however this makes things like
package obsoletion and general management less safe. Requesting the any arch
on one of the instances, or making an any arch instance would possibly be
saner.
A separate repo for "any" packages can be confusing for users and source
of new bugs (mismatched "any" and arch-specific repo, for example).
Also, the set of "any" package is not necessarily the same for all
arches (for example, for some time Python3 was only available to x86_64,
hence the x86_gcc2 repos should not have any python3 package even though
they have arch any - they would not have all the required dependencies).
The current repo setup de-duplicates them by using hardlinks, IIRC. This
can even be done after the fact, just by finding files with identical
names and replacing them with links.
--
Adrien.
Other related posts:
