Hi On Sun, Jun 06, 2010 at 01:45:00PM +0200, Jan Groenewald wrote: > >> When I untar sage as root not all files are owned > >> as root. (This is after running make as root, but still) > My query is about the file ownerships and still stands please.
Let me expand. Unlike other packages, sage does not have 'make install', or a prepared package for any distro. It copies only a sage script pointing at the files. In making headway towards system-wide installs, the files used, the untarred and built system, should be capable of being owned by root. I'm exploring the question from that angle. Of course some don't-build-as-root and sudo questions will arise, but the focus here is on a system-wide install, not the practice of individual users, who Ñ•hould of course ./configure make sudo make install in general, and for sage, preferably untar or build as themselves, then sudo cp sage and edit SAGE_ROOT. Please leave those aside for now, and look at the question of file ownership for a system-wide install. Usually, the sudo make install step would change ownership to be root. In sage's case, this affects only the sage script. I feel having many sage files in the untarred/build directories having unpredictable ownerships, potentially groups with certain elevated permissions on all the systems out there (by user/group id) is 1) inelegant and 2) dangerous. regards, Jan -- .~. /V\ Jan Groenewald /( )\ www.aims.ac.za ^^-^^ -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
