Re: [Boost-build] [bbv2] Subsequent installs to same directoryfails with install target

From: Jorge Suit Perez Ronda (josp.jorge_at_[hidden])
Date: 2006-11-10 08:04:26

it happened the same to me, I had to set  the read attribute to all from
the original files before doing "install". Is there any way that the
action copy force read permission by all after copying the file when
doing install?

regards,

Jorge
On Fri, 2006-11-10 at 13:09 +0100, Johan Nilsson wrote:
> Vladimir Prus wrote:
> > On Friday 10 November 2006 14:21, Johan Nilsson wrote:
> >> Hi,
> >>
> >> I've been using package.install to install my own libraries with
> >> headers for some time now.
> >>
> >> What I noticed now, is that when invoking "bjam install" more than
> >> once, the subsequent attempts always fail with "Permission Denied"
> >> under OpenSuse 10 (the only platform I've tested on).
> >>
> >> I don't think I've seen this before - or did I miss something?
> >
> > This is most likely caused by your UMASK settings, or something else
> > platform specific. Boost.Build uses plain 'cp' to copy files, so they
> > are created with default permission for your envirnoment.
> 
> Output of umask is '0022' (u=rwx,g=rx,o=rx).
> 
> What seems to be the cause is that the (source) headers are read-only, and 
> that this attribute propagates to the target. I guess that it should be that 
> way, or?
> 
> I've got my own source code in a Perforce depot, and Perforce by default 
> keeps files that are not opened for edit as read-only on the client.
> 
> For sources originating from cvs, e.g. Boost, it seems to "work" by default 
> (with a few exceptions as filesystem/cerrno.hpp which is read-only for me).
> 
> / Johan
> 
> 
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build