search for: available_packages_fields

...evilla writes: Lluis, So in available.packages() I could replace if (is.null(fields)) fields <- requiredFields else { stopifnot(is.character(fields)) fields <- unique(c(requiredFields, fields)) } by someting like if(is.null(fields)) fields <- getOption("available_packages_fields") if(is.null(fields)) fields <- requiredFields else { stopifnot(is.character(fields)) fields <- unique(c(requiredFields, fields)) } ? Best -k > Hi all, > I have recently been researching how available.packages and > install.packages filter packages fro...

...if (is.null(fields)) > fields <- requiredFields > else { > stopifnot(is.character(fields)) > fields <- unique(c(requiredFields, fields)) > } > > by someting like > > if(is.null(fields)) > fields <- getOption("available_packages_fields") > if(is.null(fields)) > fields <- requiredFields > else { > stopifnot(is.character(fields)) > fields <- unique(c(requiredFields, fields)) > } > > ? > > Best > -k > > > > > Hi all, > > I have recen...

...fields to the repository file is a different issue). Would it be possible to add a new option to add fields to be read by available.packages, similar to filters? The same approach for fields as for filters would avoid the two workarounds mentioned. To match it, the new option could be named "available_packages_fields". I look forward to hearing from you, Llu?s [[alternative HTML version deleted]]