Re: Release process (was Re: DarwinPorts 1.3.1)

On Aug 3, 2006, at 6:15 AM, Paul Guyot wrote:

>
> Library injection gives enough granularity to be able to  
> independently:
> - detect what the package refers to
> - prevent the package from doing dirty things
> - prevent the package from referring to things
>
> While chroot doesn't provide this granularity.
>
> I maintain that the third item isn't required at all. It changes  
> some details, but a robust package generation tool can only be  
> based on the first two items.
>
> On the box building packages, it's perfectly fine if a port A  
> refers to port B while the dependency isn't declared in the  
> portfile. We only need to add the dependency rule because the box  
> installing packages should install port B before installing port A.  
> Preventing port A to detect port B either reduces the features of  
> the package of port A (it could take advantage of port B) or will  
> make it fail (if a node fails in the dependency graph, the  
> connected nodes cannot be built either).

Doesn't that mean that without the 3th item the contents of the  
package for A would vary on whether or not port B happens to be  
installed on the package build system? That is IMHO a bad thing, this  
entire discussion seems to be about getting reproducable builds and  
not having the 3th item seems to defeat that.

Ronald

_______________________________________________
Darwinports mailing list
[email protected]
http://www.opendarwin.org/mailman/listinfo/darwinports