Re: Release process (was Re: DarwinPorts 1.3.1)

On Aug 2, 2006, at 3:17 PM, Paul Guyot wrote:

> Are you basically saying that trace mode should be used in  
> production code to do the equivalent of --without-X in configure  
> and enforce it during build and install phases?
>
> I was only thinking about using it for automatic testing. There are  
> several reasons for not requiring its use in production code. For  
> example, trace mode slows the installation process significantly.  
> Besides, the mode isn't completely protected from a port that could  
> get rid of it, for example by unsetting global variables. Finally,  
> some dependencies cannot be detected because they only happen at  
> runtime.

I don't think there's any real distinction between "production mode"  
and any other mode going forward.   End-user should (and want to) be  
using packages.  Packages should be built by the DP project on a  
regular basis for its users.  Building packages we can trust will  
require using trace mode to sandbox builds.

The only other people I would expect to be building stuff would be  
the limited number of Portfile authors, and they'll also want to use  
trace mode in their development process (at least at the validation  
stage) to ensure that the Portfile is really correct.  End-users only  
build ports today because there are no packages, not because end- 
users are good at building stuff (they're not) or enjoy the process  
(they don't).  That makes the notion of a "faster production mode"  
kind of irrelevant.

- Jordan