* [Caml-list] patch to install without 'cp'
@ 2003-04-19 1:53 Jan Schaumann
0 siblings, 0 replies; only message in thread
From: Jan Schaumann @ 2003-04-19 1:53 UTC (permalink / raw)
To: caml-list
Hi,
Suppose root has a umask of 077. Doing a 'make install' in the top
level of the ocaml distribution will install everything in a way that
will prohibit other users from accessing all the files, as 'cp' is used.
In NetBSD's Packages Collection[1] we generally use install(1) with the
appropriate flags to ensure that all modes are proper. We define:
BSD_INSTALL_PROGRAM="install -c -s -o root -g wheel -m 555"
BSD_INSTALL_SCRIPT="install -c -o root -g wheel -m 555"
BSD_INSTALL_DATA="install -c -o root -g wheel -m 444"
BSD_INSTALL_MAN="install -c -o root -g wheel -m 444"
BSD_INSTALL_PROGRAM_DIR="install -d -o root -g wheel -m 555"
BSD_INSTALL_SCRIPT_DIR="install -d -o root -g wheel -m 555"
BSD_INSTALL_DATA_DIR="install -d -o root -g wheel -m 555"
BSD_INSTALL_MAN_DIR="install -d -o root -g wheel -m 555"
I have a patch[2] to use these variables -- if you specify these or
similar variables in the distributions top-level Makefile, you can apply
it and thus ensure that all things are installed with the proper
permissions regardless of the installing users umask.
-Jan
[1] http://www.netbsd.org/Documentation/software/packages.html
[2] http://www.netmeister.org/misc/netbsd/ocaml.install.diff
--
This one's tricky. You have to use imaginary numbers, like eleventeen...
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-04-22 11:29 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-04-19 1:53 [Caml-list] patch to install without 'cp' Jan Schaumann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox