On Apr 9, 2011, at 2:13 PM, Patryk Zawadzki wrote: > 2011/4/9 Elan Ruusamäe <[email protected]>: >> so my vote goes for keeping the old .py[co] method, and perhaps change to >> make is package only .pyc, it is rather ratre somebody invokes python with >> -O option so the .pyo is to be needed. or why it was packaged in first >> place? to get files owned in case somebody invokes as root and .pyo gets >> created? perhaps package .pyc as regular files and .pyo as ghosted then. > > Not sure about PLD but I suppose we just followed what the others were > doing. Other distros did it this way so they could set proper selinux > attributes. >
Yes. Attaching SElinux xattr's to 1+ M paths forced *.pyo to be included everywhere/always in *.rpm. That *was* 5+ years ago. There's no known reason why xattr's can't be done in other ways. In fact SELinux does relabeling outside of rpm these days, there's literally no reason that *.pyo MUST be included in *.rpm 5+ years later. And 5+ years later SELinux hasn't really achieved the wide deployment desired, packaging *.pyc and adapting to changing conventions in pyton > 3.2 wasn't even conceivable 5+ years ago. 73 de Jeff
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ pld-devel-en mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
