Hey guys...i think i'd like to put my $0.02 in now.
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
I have to agree with Johannes here, the testing should happen on the dev side and there should be some type of "QOS" control for a port that we produce.
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)
not to throw a wrench in this discussion, but i did the server migration off crux.nu for the hell of it on the ppc install that i did last night, and so far every port i've tried works fine. I even built firefox 1.5 with the deps from Matts gnome repo and it worked like a charm. I know i'm going to run into some problems eventually, but hell, i'm telling yall that maybe the best was would be to just submit patches to the tree for ppc/sparc? use the repos and create tools for the two other $ARCHS to patch them to make sure the work? -j -- Jonathan Asghar phone: 512.619.0722