Am 19.10.2016 7:06 vorm. schrieb "Adrien Destugues" <
pulkomandy@xxxxxxxxxxxxx>:
wrote:
On Tue, Oct 18, 2016 at 04:38:03PM -0400, waddlesplash wrote:
On Tue, Oct 18, 2016 at 2:37 PM, Jérôme Duval <jerome.duval@xxxxxxxxx>
I fail to see the point of a "core" repo, the initial set of packages
come obviously from the stable branch of haikuports anyway, which
could then be found as a previous version of the haikuports repo.
More important, for a full rebuild, this set of core packages should
be rebuilt first, beginning with binutils and gcc. At the moment this
is a hazard to build any package before the future gcc runtime is even
available.
+1 to this.
My personal preference would be to freeze HaikuPorts for a short
period of time, fixes only during that period, and then cut it as
"r1alpha5" or whatever, committing only security/bugfix changes to
that branch, while master continues on its merry way.
I already created the release branch, it lives on my fork of haikuports
for now. It is a subset of the main repo, because I don't have 50 years
to spend fixing all the recipes. So I picked only what's currently in
our binary repo, and will probably remove
