Build an R package tarball without divulging your user name in the tarball
up vote
9
down vote
favorite
2
In R CMD build, the ID of the user is automatically inserted into the DESCRIPTION file. This is problematic because I work in a corporate computing environment and I do not want to divulge my user ID.
Reproducible example:
git clone git@github.com:tidyverse/reprex
R CMD build reprex
rm -rf reprex
tar -xf reprex*tar.gz
grep Packaged reprex/DESCRIPTION
Current output:
Packaged: 2018-11-06 14:01:50 UTC; <MY USER ID>
Desired output
Packaged: 2018-11-06 14:01:50 UTC;
r r-package
asked Nov 6 at 14:07
landau
1,109921
add a comment |
up vote
9
down vote
favorite
2
In R CMD build, the ID of the user is automatically inserted into the DESCRIPTION file. This is problematic because I work in a corporate computing environment and I do not want to divulge my user ID.
Reproducible example:
git clone git@github.com:tidyverse/reprex
R CMD build reprex
rm -rf reprex
tar -xf reprex*tar.gz
grep Packaged reprex/DESCRIPTION
Current output:
Packaged: 2018-11-06 14:01:50 UTC; <MY USER ID>
Desired output
Packaged: 2018-11-06 14:01:50 UTC;
r r-package
asked Nov 6 at 14:07
landau
1,109921
Why don't you just remove the name and re-compress it?
– Aravind Voggu
Nov 9 at 3:23
Doesn't seem too hard now that you mention it, but it still feels like something I should not have to clean out manually.
– landau
Nov 9 at 3:33
I added a one line script. That would be much easier than going and changing the internals, then you'll have to make changes every time you update your language. If you're using a build system, try adding this to it. Travis should have post build hooks and is free for opensource projects, try it, it's easy. Or add the script as a bash alias so you don't have to type all of it everytime.
– Aravind Voggu
Nov 9 at 3:37
add a comment |
up vote
9
down vote
favorite
2
up vote
9
down vote
favorite
2
2
In R CMD build, the ID of the user is automatically inserted into the DESCRIPTION file. This is problematic because I work in a corporate computing environment and I do not want to divulge my user ID.
Reproducible example:
git clone git@github.com:tidyverse/reprex
R CMD build reprex
rm -rf reprex
tar -xf reprex*tar.gz
grep Packaged reprex/DESCRIPTION
Current output:
Packaged: 2018-11-06 14:01:50 UTC; <MY USER ID>
Desired output
Packaged: 2018-11-06 14:01:50 UTC;
r r-package
asked Nov 6 at 14:07
landau
1,109921
In R CMD build, the ID of the user is automatically inserted into the DESCRIPTION file. This is problematic because I work in a corporate computing environment and I do not want to divulge my user ID.
Reproducible example:
git clone git@github.com:tidyverse/reprex
R CMD build reprex
rm -rf reprex
tar -xf reprex*tar.gz
grep Packaged reprex/DESCRIPTION
Current output:
Packaged: 2018-11-06 14:01:50 UTC; <MY USER ID>
Desired output
Packaged: 2018-11-06 14:01:50 UTC;
r r-package
r r-package
asked Nov 6 at 14:07
landau
1,109921
asked Nov 6 at 14:07
landau
1,109921
edited Nov 9 at 2:55
asked Nov 6 at 14:07
landau
1,109921
asked Nov 6 at 14:07
landau
1,109921
asked Nov 6 at 14:07
landau
1,109921
1,109921
Why don't you just remove the name and re-compress it?
– Aravind Voggu
Nov 9 at 3:23
Doesn't seem too hard now that you mention it, but it still feels like something I should not have to clean out manually.
– landau
Nov 9 at 3:33
I added a one line script. That would be much easier than going and changing the internals, then you'll have to make changes every time you update your language. If you're using a build system, try adding this to it. Travis should have post build hooks and is free for opensource projects, try it, it's easy. Or add the script as a bash alias so you don't have to type all of it everytime.
– Aravind Voggu
Nov 9 at 3:37
add a comment |
Why don't you just remove the name and re-compress it?
– Aravind Voggu
Nov 9 at 3:23
Doesn't seem too hard now that you mention it, but it still feels like something I should not have to clean out manually.
– landau
Nov 9 at 3:33
I added a one line script. That would be much easier than going and changing the internals, then you'll have to make changes every time you update your language. If you're using a build system, try adding this to it. Travis should have post build hooks and is free for opensource projects, try it, it's easy. Or add the script as a bash alias so you don't have to type all of it everytime.
– Aravind Voggu
Nov 9 at 3:37
Why don't you just remove the name and re-compress it?
– Aravind Voggu
Nov 9 at 3:23
Why don't you just remove the name and re-compress it?
– Aravind Voggu
Nov 9 at 3:23
Doesn't seem too hard now that you mention it, but it still feels like something I should not have to clean out manually.
– landau
Nov 9 at 3:33
Doesn't seem too hard now that you mention it, but it still feels like something I should not have to clean out manually.
– landau
Nov 9 at 3:33
I added a one line script. That would be much easier than going and changing the internals, then you'll have to make changes every time you update your language. If you're using a build system, try adding this to it. Travis should have post build hooks and is free for opensource projects, try it, it's easy. Or add the script as a bash alias so you don't have to type all of it everytime.
– Aravind Voggu
Nov 9 at 3:37
I added a one line script. That would be much easier than going and changing the internals, then you'll have to make changes every time you update your language. If you're using a build system, try adding this to it. Travis should have post build hooks and is free for opensource projects, try it, it's easy. Or add the script as a bash alias so you don't have to type all of it everytime.
– Aravind Voggu
Nov 9 at 3:37
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
+50
I'm not aware of doing this internally, but, why don't you just remove the ID and repackage it?
git clone git@github.com:tidyverse/reprex
R CMD build reprex
rm -rf reprex
tar -xf reprex*tar.gz
grep -l "Packaged" reprex/DESCRIPTION | xargs sed 's/UTC;.*/UTC;/' > reprex/DESCRIPTION
Now compress it again with tar. Probably add this to your build system.
answered Nov 9 at 3:34
Aravind Voggu
751413
1
Yeah, I think this is the appropriate way to go. Reminds me of github.com/r-lib/pkgdown/issues/492, actually.
– landau
Nov 9 at 3:42
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
+50
I'm not aware of doing this internally, but, why don't you just remove the ID and repackage it?
git clone git@github.com:tidyverse/reprex
R CMD build reprex
rm -rf reprex
tar -xf reprex*tar.gz
grep -l "Packaged" reprex/DESCRIPTION | xargs sed 's/UTC;.*/UTC;/' > reprex/DESCRIPTION
Now compress it again with tar. Probably add this to your build system.
answered Nov 9 at 3:34
Aravind Voggu
751413
1
Yeah, I think this is the appropriate way to go. Reminds me of github.com/r-lib/pkgdown/issues/492, actually.
– landau
Nov 9 at 3:42
add a comment |
up vote
1
down vote
accepted
+50
I'm not aware of doing this internally, but, why don't you just remove the ID and repackage it?
git clone git@github.com:tidyverse/reprex
R CMD build reprex
rm -rf reprex
tar -xf reprex*tar.gz
grep -l "Packaged" reprex/DESCRIPTION | xargs sed 's/UTC;.*/UTC;/' > reprex/DESCRIPTION
Now compress it again with tar. Probably add this to your build system.
answered Nov 9 at 3:34
Aravind Voggu
751413
1
Yeah, I think this is the appropriate way to go. Reminds me of github.com/r-lib/pkgdown/issues/492, actually.
– landau
Nov 9 at 3:42
add a comment |
up vote
1
down vote
accepted
+50
up vote
1
down vote
accepted
+50
+50
I'm not aware of doing this internally, but, why don't you just remove the ID and repackage it?
git clone git@github.com:tidyverse/reprex
R CMD build reprex
rm -rf reprex
tar -xf reprex*tar.gz
grep -l "Packaged" reprex/DESCRIPTION | xargs sed 's/UTC;.*/UTC;/' > reprex/DESCRIPTION
Now compress it again with tar. Probably add this to your build system.
answered Nov 9 at 3:34
Aravind Voggu
751413
I'm not aware of doing this internally, but, why don't you just remove the ID and repackage it?
git clone git@github.com:tidyverse/reprex
R CMD build reprex
rm -rf reprex
tar -xf reprex*tar.gz
grep -l "Packaged" reprex/DESCRIPTION | xargs sed 's/UTC;.*/UTC;/' > reprex/DESCRIPTION
Now compress it again with tar. Probably add this to your build system.
answered Nov 9 at 3:34
Aravind Voggu
751413
answered Nov 9 at 3:34
Aravind Voggu
751413
answered Nov 9 at 3:34
Aravind Voggu
751413
answered Nov 9 at 3:34
Aravind Voggu
751413
751413
1
Yeah, I think this is the appropriate way to go. Reminds me of github.com/r-lib/pkgdown/issues/492, actually.
– landau
Nov 9 at 3:42
add a comment |
1
Yeah, I think this is the appropriate way to go. Reminds me of github.com/r-lib/pkgdown/issues/492, actually.
– landau
Nov 9 at 3:42
1
1
Yeah, I think this is the appropriate way to go. Reminds me of github.com/r-lib/pkgdown/issues/492, actually.
– landau
Nov 9 at 3:42
Yeah, I think this is the appropriate way to go. Reminds me of github.com/r-lib/pkgdown/issues/492, actually.
– landau
Nov 9 at 3:42
add a comment |
draft saved
draft discarded
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53173552%2fbuild-an-r-package-tarball-without-divulging-your-user-name-in-the-tarball%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Why don't you just remove the name and re-compress it?
– Aravind Voggu
Nov 9 at 3:23
Doesn't seem too hard now that you mention it, but it still feels like something I should not have to clean out manually.
– landau
Nov 9 at 3:33
I added a one line script. That would be much easier than going and changing the internals, then you'll have to make changes every time you update your language. If you're using a build system, try adding this to it. Travis should have post build hooks and is free for opensource projects, try it, it's easy. Or add the script as a bash alias so you don't have to type all of it everytime.
– Aravind Voggu
Nov 9 at 3:37