|
Boost : |
From: Beman Dawes (bdawes_at_[hidden])
Date: 2004-11-01 12:51:19
At 09:22 AM 11/1/2004, David Abrahams wrote:
>Vladimir Prus <ghost_at_[hidden]> writes:
>
>> Aleksey Gurtovoy wrote:
>>
>>>> The first two archives does not give write permissions to the user
(for
>>>> the unarchived files).
>>>
>>> That's intentional. After all, normally you shouldn't be modifying
>>> anything in the distribution. Or should you?
>>
>> No unix source package I ever downloaded had read-only files. That
gives
>no
>> protection, really. If I unintentionally remove some files, I can just
>> reinstall. If I want to edit them, I'll edit them anyway. Write
>protection
>> will just get in the way. BTW, just like it gets in the way with
>> Boost CVS
>> -- somehow all files are read only and I constantly have to change
>> permissions or tell Emacs to override them.
>
>Personally I like that. I don't tell Emacs to override them, I
>use `C-x v v' to "cvs edit" them.
>
>There are CVS options to control this. In fact, unless you have
>CVSREAD set in your environment, CVS checks out writable files.
There must be more to the story than that. I don't have CVSREAD set, but
always get read-only files from the main CVS yet read-write files from the
sandbox. It's a mystery!
--Beman
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk