Re: 'git clone,' build makes user non-writable files (should be option keep user-writable)

[Beat Bolli <dev@drbeat.li>]

On Fri, Jul 15, 2022 at 03:35:49AM -0700, David Chmelik wrote:

[resend with reply-to-all]

> What did you do before the bug happened?
> 'git clone,' built various software (with gcc, BSD & GNU make, autotools,
> cmake, etc.)
> 
> What did you expect to happen?
> Option: keep cloned/built/etc. files user-writable.
> 
> What happened instead?
> Needed chmod or 'sudo rm -rf.'
> 
> What's different between what you expected and what actually happened?
> Option: keep cloned/built/etc. files user-writable, otherwise (has been said
> 15+ years) encourages 'sudo rm -rf.'
> 
> Anything else you want to add:
>         I try/test/debug (and report bugs) many software commits but don't
> commit so need cloned/built/etc. files writable as user & even system-wide
> options: who hasn't made 'rm -rf' mistakes? (unrelated but someone might
> claim is: I don't use non-UNIX-like OS that shell alias 'rm -rf' to confirm
> every file (potentially thousands) and though made my own alias (confirm
> once) it's longer, sometimes unavailable so don't always use (many people
> don't)... software should always have user-writable files option.)  Below
> indicates GNU/Linux but also have often used git on *BSD/Unix.  I'm not on
> git mailing list but you can CC me all replies.

When building software as the current user, the build artefacts are
owned by this user.

Are you building the software using Docker containers that run as root?

Regards, Beat