Maybe a further thing to consider is to introduce an environment
variable by which one can avoid `add_build_stamp_to_description_file()`
and any other calls altogether which affect bitwise reproducibility
during the build process. If two users build the same package on exactly
the same
Another thing to consider if one wants to anonymize the build is the
UID/GID of the files in the tarball. So there might be a need for a
R_BUILD_UID and R_BUILD_GID, e.g. by setting those to 32767
("nobody").
/Henrik
On Fri, Jan 25, 2019 at 9:25 AM Will L wrote:
>
> Thanks, Kurt.
>
> I think I
Thanks, Kurt.
I think I now have enough time to write a patch. What are the steps? I have
read https://www.r-project.org/bugs.html#how-to-submit-patches but I do not
seem to have permission to create a Bugzilla account at
https://bugs.r-project.org/bugzilla/.
Will
On Mon, Nov 12, 2018 at 2:46
> Will L writes:
> To R-devel,
> In `R CMD build`, the ID of the user is automatically inserted into the
> DESCRIPTION file, e.g.
> Packaged: 2018-11-06 14:01:50 UTC;
> This is problematic for those of us who work in corporate settings. We must
> not divulge our user IDs in the packages
To R-devel,
In `R CMD build`, the ID of the user is automatically inserted into the
DESCRIPTION file, e.g.
Packaged: 2018-11-06 14:01:50 UTC;
This is problematic for those of us who work in corporate settings. We must
not divulge our user IDs in the packages we develop and release.
Jim
