On Sat, 09 Sep 2006 17:30:37 +0200, Hisham Muhammad <[EMAIL PROTECTED]> wrote:
> On 9/9/06, Hisham Muhammad <[EMAIL PROTECTED]> wrote: >> On 9/9/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote: >> > Added installation of unmanaged files to SymlinkProgram >> >> Installation of unmanaged files is/should not be made at >> SymlinkProgram, but at InstallPackage and Compile. You don't want >> unmanaged files to be re-copied every time you switch versions using >> SymlinkProgram, for example. > > I missed a previous thread about this, sorry, but looking closer at > the issue, I do see that having a way to install unmanaged files from > the command line could be a good thing. But I still think it should > not be part of SymlinkProgram. I don't think copying files around the > system is conceptually a task for SymlinkProgram. > > One could start imagining complex schemes for handling unmanaged > files, kind of like UpdateSettings, but unmanaged files are, well, > unmanaged. :) The very point of having "unmanaged files" was the > realization that there is no good way to manage them, so I'm skeptical > about schemes for automating their control... The changes offering to > remove files in RemoveProgram look good, but I fear we won't be able > to go much further than that. :\ > Well, I may see unmanaged files in another way. To me the unmanaged files are files that can't be symlinked (kernel modules, /etc/passwd etc), or files that _have_ to be in a directory which we don't support as links in the program directory. So in a way it's managed files, just that they hae certain demands. -- /Jonas Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ _______________________________________________ gobolinux-devel mailing list [email protected] http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
