roucaries> No the problem is not probing the cpu/cpuinfo...
Well, if the CPU info could be probed from shell, I'd argue that's better than unpacking a binary. roucaries> The problem is the base64 encoded binary. Why is this bad. I agree that it is esthetically displeasing, but *in this instance*, why is it harmful? roucaries> I ma solving this by pre-depends on a binary package and roucaries> run the binary from the preinstalled package. I would have been less caustic in my reply than Adam, but made the same point. Having multiple packages is more complex, especially in a situation where the binary in question is only used by the preinst. It may be there are concerns I'm not seeing that make the current arrangement worse than taht. But let's actually articulate them.