Manoj Srivastava wrote:
Actually, adding to the utility set could be an issue, especially for low memory (ipaq/Zaurus, anyone?) or embedded systems.
Since embedded systems are most likely going to use dpkg or something dpkg-like in strange ways (not installing all files), theres going to have to be much possible work on assumptions on embedded platforms. I could see it going the way of Familiar, where you install ncurses and dont end up with libpanel! This isn't directly related to the current conversation, but if embedded platforms do end up with the features to be able to exclude files there must be some sort of policy to avoid broken dependencies on theese platforms. Those platforms could be even *worse* than this debacle. Hopefully such people convince maintainers to split such packages up instead of some horribly moronoic file dependency system. If theres one thing I /HATE/ about rpm is file deps.
Not me personally. I looked at the size (~19kB), and the feature set, and I saw can see scenarios in which a small network aware tool would be helpful in diagnosis (low probability ones,
Or recovery from non-local tape dumps. -- Scott Dier <dieman@ringworld.org> http://www.ringworld.org/ -- To UNSUBSCRIBE, email to debian-policy-request@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org