Package: eatmydata Version: 82-2 Severity: normal This is sort of insane - using dpkg-dev just to get current architecture. dpkg-dev pulls in binutils, some perl stuff, patch, others -- 27 extra megabytes. I use it on systems with a highly space-constrained flash-based storage to keep the storage from wearing out by eliminating syncs, and now it requires way more extra unused packages than it can save _just_ for dpkg --print-architecture.
But I really wonder: _why_ it uses that? What dpkg --print-arch gives us? I can install foreign dpkg, or run foreign binaries whose architecture has nothing to do at all with the one of dpkg. What's the reason to ask current architecture of dpkg to start with? Thanks, /mjt -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
