Re: Can GUB-build stable/2.20 [was Re: Still cannot build GUB with stable/2.20 branch]

[David Kastrup]

Knut Petersen <address@hidden> writes:

> On 21.03.19 12:04, Phil Holmes wrote:
>
>> Anyway - it would seem easiest just to create a 'lilypond' group. 
>> Does that seem the best way forward? 
>
> In rsync-lily-doc.py we have:
>
>      system ('rsync --exclude "*.signature" --hard-links
> --delay-updates --delete --delete-after --stats --progress -pgorltvu
> -e ssh . %s/%s/' % (options.destination, branch_dir))
>
> In rsync-test.py we have:
>
>    system ('rsync --hard-links --delay-updates --delete --delete-after
> --stats --progress -pgorltvu -e ssh . %s/%s/' % (options.destination,
> target))
>
> Group and ownership are preserved here. But "preserved" means that the
> numeric group / user id is preserved, not the literal name mapped to
> the GID/UID on the two systems.

Sure about that?

        -o, --owner
                This  option  causes rsync  to  set  the owner  of  the
                destination file to be the same as the source file, but
                only  if  the  receiving  rsync is  being  run  as  the
                super-user  (see  also  the  --super  and  --fake-super
                options).  Without this option, the owner of new and/or
                transferred files are  set to the invoking  user on the
                receiving side.

                The preservation  of ownership will  associate matching
                names by  default, but  may fall back  to using  the ID
                number   in   some    circumstances   (see   also   the
                --numeric-ids option for a full discussion).

        -g, --group
                This  option  causes rsync  to  set  the group  of  the
                destination file to be the same as the source file.  If
                the receiving program is  not running as the super-user
                (or if --no-super was  specified), only groups that the
                invoking user on the receiving side is a member of will
                be preserved.  Without this option, the group is set to
                the default group of the invoking user on the receiving
                side.

                The  preservation of  group information  will associate
                matching names by  default, but may fall  back to using
                the  ID  number in  some  circumstances  (see also  the
                --numeric-ids option for a full discussion).


-- 
David Kastrup