...hat build policy options would fix this problem?

Right, who knows? Who wants to spend the time worrying about it? So what I do is create a user, build a perl in that user's home directory, and update the user's path. Because I'm a web developer, I do the same with apache. Then the application runs from that user's context instead of a system context.

Sure, I have to rely on what the distro provides for most things (networking, a sane compiler, and an easy to use update system). So I start with a distro that I trust for the things I need to trust it with. But for my application, I build the critical components myself.

I don't know how many times I've seen where people deploy thier app using the system provided stuff for critical components (like perl), and then their app busts when they do an update. If the critical core components of the app would have been bundled with the app, the problem would have been completely avoided.

trwww