In article <[EMAIL PROTECTED]>, Martin Costabel <[EMAIL PROTECTED]> wrote:
> > 1. Have fink build as non-root. However, to do this properly I think > > this requires the use of fakeroot. If anyone wants to port fakeroot, > > they'd be doing the fink community an enormous favour. > > Probably, but this wouldn't have helped here. The catastrophe happens > when the package is installed by dpkg, not when it is built. Right. But if I were wondering about fink accidentally causing serious system damage, I would have guessed the build process. If anyone does manage to port fakeroot, fink should certainly use it. > > 2. After the dpkg is built, fink should check it to make sure that all > > the files are within %p (or within other directories somehow explicitly > > mentioned in the .info file). > > I would rather hope that in future the kind of error that happened here > will somehow get detected by human eyes before it can do much > destruction. I would regret it if my oversight were the reason for the > introduction of some heavy bureaucracy into fink that would be useful > only in extremely exceptional cases. I really see this as a simple sanity check on the dpkg. There are very few packages that install outside of %p and no other package info files need be affected. -- Ashley Yakeley, Seattle WA ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
