[Bug 480685] fontforge multilib conflict

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=480685


Kevin Fenzi <kevin at tummy.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED




--- Comment #1 from Kevin Fenzi <kevin at tummy.com>  2009-01-21 11:40:13 EDT ---
Well, I'm not sure there is an easy way around this one. ;( 
Those are python compiled files that are made during build. 

Of course the x86_64 and i386 builds happen at slightly different times, so the
generated files differ at least in timestamps. ;( 

Possible hacks: 

- Move them to the python arch directory so they are different per build. 
Thats kinda bad though as they are really the same files, so it would be
duplication. 

- Set the timestamps on them from something else (the source exepthook.py?)
This would be a bit misleading however. 

- Drop the python file entirely for now. This is bad because this file runs the
exception hook for gui sessions, so users can see when they get an exception
instead of it going to stderr. ;( 

I'm open to other ideas...

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.