Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

insertPackage could accept "fields" argument passed to write_PACKAGES #53

Closed
jangorecki opened this issue Jul 31, 2016 · 10 comments
Closed

Comments

@jangorecki
Copy link
Contributor

So user can have better control over what metadata are being part on the PACKAGES index file.

@jangorecki jangorecki changed the title insertPackage could accept fields argument passed to write_PACKAGES insertPackage could accept "fields" argument passed to write_PACKAGES Jul 31, 2016
jangorecki added a commit to jangorecki/drat that referenced this issue Jul 31, 2016
@eddelbuettel
Copy link
Owner

The idea of opening a issue ticket is to give me a moderate and reasonable amount of time to actually look at the ticket, read it and comment.

Immediately following up with PR is useless.

Please motivate why all users of drat need a new field.

@eddelbuettel
Copy link
Owner

A priori I am not in favour of doing anything which R itself does not do. One key argument for drat is that everything is as plain vanilla as possible, and that the exact same tools are used.

@jangorecki
Copy link
Contributor Author

but this is what R do tools::write_PACKAGES. Why not use metadata from DESCRIPTION file to build PACKAGES index? I would say this is a feature of base R / tools vs drat at the moment.

@eddelbuettel
Copy link
Owner

oh, I see -- you got a point there. makes it way more elegant and I am starting to warm up to it.

patch then lets you clobber your PACKAGE with whatever you want to put, everybody else gets what they always had and we have a path forward.

I think we can do that. lemme give it a day.

@jangorecki
Copy link
Contributor Author

should be doable with ... instead of new argument

@eddelbuettel
Copy link
Owner

eddelbuettel commented Jul 31, 2016

or new (to us) argument with default value that is set, provided we don't mess with the order

jangorecki added a commit to jangorecki/drat that referenced this issue Jul 31, 2016
@jangorecki
Copy link
Contributor Author

Fields expected by default won't be reordered, new lines from provided fields are after the defaults. What do you think about ... in 66e407a?

@eddelbuettel
Copy link
Owner

looks good. Is ...=... legit? Don't think I have seen that...

jangorecki added a commit to jangorecki/drat that referenced this issue Jul 31, 2016
@jangorecki
Copy link
Contributor Author

While ...=... is legit, it shouldn't be here, as write_PACKAGES doesn't have ... arg. Updated in latest commit.

@eddelbuettel
Copy link
Owner

Well caught, thank you.

jdrussell pushed a commit to jdrussell/drat that referenced this issue Jun 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants