Johannes Winkelmann wrote:
Hi,
I'm not quite sure here. Adapting the base and opt ports for CRUX/SPARC took me only a few days, and I did it alone. In real life, those changes don't happen all at the same time, so after the initial port, it's like 1 or 2 updates per day.
What makes you believe it's not acceptable?
not acceptable for little communities because they remains 1 or 2 updates per day if the number of ports remains of little entity, as it is now ... in order consider that "tests" can be made only by $ARCH developers
Are you currently using any tools to sync your trees with the x86 one for those ports which require changes?
no, we've in mind to have /usr/ports/x86 and /usr/ports/ppc in the second tree will exists only the ports that needs to be modified on ppc
if the $ARCH community can instead use the "master" ports tree (it should be ok in the 90% of cases)
However, this only works if there's a single master tree. We from the x86 port lost a good number of important projects due to Daniel's move to x86_64, and chances are this will happen more often in the future. I don't think that a model with a single master tree is realistic for the future, considering the size of our team.
our idea instead is based on a "master" single tree where we should merge forces :P -- Giulivo Navigante http://cruxppc.sunsite.dk