2007/7/20, Lucas C. Villa Real <[EMAIL PROTECTED]>: > On 7/16/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > On 7/16/07, Carlo Calica <[EMAIL PROTECTED]> wrote: > > > 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>/. > > Yes, that makes sense. It sounds a lot more helpful to have a > PostInstall script capable of doing that. > Yes, post install shouldn't touch /Programs/<app>/<version>/, as that should be done during install. Instead my idea was to have a file InstallFunctions, which would look more like a recipe, with some variables, like 'required_users', for repeated tasks, and some functions Pre_install/Post_Install, for everything else. Things that could/should be in those functions is calls to some sort of API, that has functions like update_mime_database and update_gconf. But maybe then those functions aren't needed and only a list of which updating functions would be needed. But then again OpenSSH uses functions to generate host keys.
What do we want to do with PostInstall? -- /Jonas _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
