Mike Hommey <[EMAIL PROTECTED]> wrote: > On Wed, Oct 11, 2006 at 07:55:54AM +0200, Frank Küster <[EMAIL PROTECTED]> > wrote: >> Yes, that's the ideal solution. In the real world, my suggestion may >> improve the situation faster. >> >> Just got an other idea, slower too, but makes the "ideal solution" more >> realistic: Someone writes a tool analogous to piuparts, but not for >> install/upgrade, but for package building. This tool would check >> whether any tool used in the build process does nasty things, like >> accessing $HOME, communicating over the network, assuming existence of >> particular files in /sys or /proc, and the like. > > Something similar should be done with package installations... I hate > that my /root is cluttered with .gconf, .anthy, .gnome, .gnupg, .qt ... > while I never run that kind of software as root...
This could be done inside piuparts, couldn't it? Or isn't that kind of behavior already checked, since piuparts complains about all leftover files on the system? Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
