Re: Ownership not set for some files by make install

VK> Please note, that simply owning all files in the tarball by VK> root won't help in the case of building by user and installing VK> by root without chown'ing the source tree (which is the case). If those are generated files, then it's not really our problem. We can't know what site policy is about the ownership of those files. root is plausible, but what about the group? We also don't know what tools will be available. For example, gnu tar has an option to have root also set the user of the files (ie, to root), but that's an extension. Finally, XEmacs is used on systems where chown doesn't even make sense and may not be available. This really has to be the responsibility of OS distros and individual admins mostly. If you want to supply a script for your platform we can include that (see the blessmail target, for example). But anything we do is going to displease somebody, and probably we should not do it automatically. If you know of an app that is as portable cross-platform as XEmacs that does that kind of thing, feel free to refer us to it (preferably, give us a detailed summary of their system as well as the URL). -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.