[haiku-development] Re: [haiku] Re: Future releases? Recommend nightlies? gcc2?
- From: "Adrien Destugues" <pulkomandy@xxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 05 Dec 2016 16:29:11 +0000
5 décembre 2016 17:21 "kallisti5" <kallisti5@xxxxxxxxxxx> a écrit:
Actually, while that would be cool, I was reaching for a far more
closer goal: having a packaging scheme that allows the packages to be
identical for gcc2h, and gcc5h; ie. there wouldn't be a primary and
secondary architecture anymore, but only two equal different ones.
I may have worded that poorly, though :-)
This would be ideal (and i'm under the opinion it should have been
originally designed as such), but I don't think we have anyone to actually
work on it at the moment.
We decided to not move gcc2 libs too much to avoid problems with BeOS and old
Haiku apps relying on hardcoded or partially hardcoded paths. People working on
haikuporter side remember the effort introducing find_paths or find_directory
to all apps just for the settings/data dirs, we don't want to be patching
everything again for library/binary dir changes.
Maybe there are other solutions, like using "abstract" paths in packages
($binDir, etc) and resolving at install time, but I see many ways this could
not work as expected.
Our PM is *extremely* complex in spots
with lots of surface area for regressions. (all learned from just
trying to remove the url from repos)
unit tests?
I'm afraid if we decide to "rework all of our package management" now
the project will never see a release.
We can make such changes after beta1, or in the R2 branch. No need to do
everything for beta1. Of course if we want to change things from one beta to
another, we should think about how to migrate stuff (including all existing
packages and Haiku installs).
--
Adrien.
Other related posts:
