From: Adrien Nader <adrien@notk.org>
To: oliver <oliver@first.in-berlin.de>
Cc: Gerd Stolpmann <info@gerd-stolpmann.de>,
John Whitington <john@coherentgraphics.co.uk>,
caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] ANN: CamlPDF 1.7
Date: Sun, 18 Aug 2013 14:04:21 +0200 [thread overview]
Message-ID: <20130818120421.GA26067@notk.org> (raw)
In-Reply-To: <20130815183912.GA11369@siouxsie>
On Thu, Aug 15, 2013, oliver wrote:
> On Thu, Aug 15, 2013 at 06:17:19PM +0200, Gerd Stolpmann wrote:
> > Looks like Oliver installed as root, and maybe there was a restrictive
> > umask. In that case, setting a better umask (e.g. umask 002) before
> > "make install" would be the solution. But that's the user's problem,
> > IMHO.
>
>
>
> Yes, of course I installed as root (via sudo).
> Umask might be the reason, yes.
> And I also had that problem with some other libraries.
It's a fairly common mistake. It's not very dangerous, until you change
your libc that is. Installing through "su" or without the umask is the
right way to do it.
> An installation can also set the
> permissions of installed files accordingly to what is needd.
> This might be added for this kind of install procedure.
It's better to just use the root account, with the right perms (which is
the default) since you'll never get full coverage.
--
Adrien Nader
next prev parent reply other threads:[~2013-08-18 12:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 11:21 John Whitington
2013-08-15 14:21 ` oliver
2013-08-15 14:28 ` John Whitington
2013-08-15 16:17 ` Gerd Stolpmann
2013-08-15 18:39 ` oliver
2013-08-18 12:04 ` Adrien Nader [this message]
2013-08-18 14:04 ` Florent Monnier
2013-08-18 18:23 ` oliver
2013-08-15 18:40 ` oliver
2013-08-15 18:42 ` oliver
2013-08-16 10:53 ` Armaël Guéneau
2013-08-16 11:06 ` John Whitington
2013-08-16 11:45 ` Armaël Guéneau
2013-08-16 14:26 ` John Whitington
2013-08-21 12:01 ` oliver
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130818120421.GA26067@notk.org \
--to=adrien@notk.org \
--cc=caml-list@inria.fr \
--cc=info@gerd-stolpmann.de \
--cc=john@coherentgraphics.co.uk \
--cc=oliver@first.in-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox