Scott Rotondo wrote: > Part of the problem seems to be that there is no good place to keep the > source code. The choices seem to be: > > (a) Keep the source in an unknown, uncontrolled location (e.g. someone's home > directory)
Sources in someone's home directory can't be used for /contrib, since the source juicer build daemon used to build contrib packages won't be able to find them there. > Couldn't we partition SFW into "release" and "contrib" trees and get the > best of both worlds? Isn't "SFW contrib" just the Companion CD with a new name? It unfortunately falls into the same trap as any SFW change - not enough people to do the work, and given the way Source Juicer works, seems mostly pointless. -- -Alan Coopersmith- alan.coopersmith at sun.com Sun Microsystems, Inc. - X Window System Engineering