The recent redhat-rpm-config change and you

[Florian La Roche]

On Tue, Jun 21, 2005 at 03:06:40PM -0400, John Dennis wrote:
> On Tue, 2005-06-21 at 14:36 -0400, Peter Jones wrote:
> > On Tue, 2005-06-21 at 14:18 -0400, John Dennis wrote:
> > > On Tue, 2005-06-21 at 14:07 -0400, Peter Jones wrote:
> > > 
> > > > It does?  I don't _think_ I've changed anything related to that...
> > > 
> > > It depends on how the interpreter reads the file, imports are compiled.
> > 
> > So we probably want to think very hard about making it _not_ do that
> > unless you try very hard.
> 
> Why do you want to defeat this feature? If python is properly packaged
> in the rpm and the security policy is aware of where the python files
> are and who can write them then I don't see a problem. I only see a
> problem when these constraints are violated (albeit too frequently).

We don't control enough packages to have them all fixed. So this is
more of a burden then help to get them compiled if they are missing.

greetings,

Florian La Roche