On 7/16/07, Carlo Calica <[EMAIL PROTECTED]> wrote: > On 7/16/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote: > > On 7/16/07, Carlo Calica <[EMAIL PROTECTED]> wrote: > > > > > > Do you mean from "make install" or PostInstall? I would argue that > > > "make install" shouldn't alter passwd/shadow/group. The makefile > > > should be patched and PostInstall used instead. > > > > Either will fail with chroot compile. Our PostInstall script needs > > adjustments badly -- one cannot write outside $target from inside > > PostInstall. Jonas had some suggestions on how to allow that in a > > similar fashion that's used to allow unmanaged files to be touched, > > but that would bring some more script files. > > > > In my opinion, PostInstall could be swept away.. I don't remember > > having seen any package or recipe using it (just in case there is > > some, its Resources/FileHash is probably getting broken after the > > script is run...) > > Isn't OpenSSH using it to generate keys? Running PostInstall outside > the sandbox might be ok. The sandbox was a neat idea but I don't know > if its actually helpful. Allowing the package to define the holes in > the sandbox effectively removes the sandbox. Unmanaged_files makes > sense for recipes because we're fighting upstreams "make install" but > PostInstall is entirely ours. > > In order to keep R/FileHash clean, PostInstall should only modify > Settings. If we remove the sandbox, anywhere but $target.
Or rather, anywhere but any /Programs/<app>/<version>/. -- Hisham _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
