On Thu, Jun 17, 2010 at 9:56 AM, Dan McGee <[email protected]> wrote: > This is one of those "seems like a good idea but why" patches. Yes, > we'll save milliseconds in building a package, but what if someone has > a legit reason for putting libraries or binaries in an 'any' package? > I'm going to -1 this one. > But "any" means that there's no arch dependant code in the package?
strip(1) can't take the debug symbols out of a .py last time I checked. Seems like there's no organization. :/ Even namcap should throw an error if it finds an elf in an "-any" package. To think I was going to propose /libexec Andres P
