Ticket #14796 (pike): please commit

Jordan K. Hubbard jkh at apple.com
Mon Mar 31 09:47:08 PDT 2008


On Mar 31, 2008, at 6:55 AM, Guido Soranzio wrote:

> I meant a simple hosting infrastructure outside of the subversion
> repository where the submitters and the committers could upload and
> share their precompiled packages/archives: we already have the
> archive mode and the support for RPM.

That's a nice idea in theory, and finding such a place to stick such  
things on MacOSForge would be comparatively simple, but I think that's  
a recipe for failure and bizarre behavior until such time as we get  
all the submitters and committers building things in a consistent way.

What I mean is, committer A could be building on Tiger/PPC, committer  
B on Leopard 10.5.0 and committer C on Leopard 10.5.2 (just to name 3  
of the many possible permutations).  Now they all go to upload their  
bits to a common place which others start to download and depend on.   
Will it work?  Who knows?  You could, of course, put big warning signs  
up saying "Do not build on anything but 10.5.2/i386 if you are going  
to upload here!!" but people don't read signs, so now what?

I think a way of enforcing consistency in the build process is a  
prerequisite to a precompiled pile of bits that just anyone can  
contribute to.  Having a centralized build infrastructure create them  
would, at least, eliminate one half of the problem.

- Jordan



More information about the macports-dev mailing list