`as_pkgrefs("DESCRIPTION")` and `export_description(rang)`

[chainsawriot]

Again, we have all the ingredients. The good things about this is that as_pkgs can look for Remotes for possible Github packages.

For export_description, we can dump x=handle@uid (Github package) in the Remotes field of the DESCRITION file.

[schochastics]

@chainsawriot I can tackle this one though I am not sure I understand the purpose of it. Is it supposed to read and write package DESCRIPTIONS? or create specific DESCRIPTION files for compendia?

[chainsawriot]

@schochastics

Is it supposed to read and write package DESCRIPTIONS? or create specific DESCRIPTION files for compendia?

I think we can think about as_pkgrefs("DESCRIPTION") first, because for reading we can think about them (package DESCRIPTION and compendium DESCRIPTION, e.g. from rrtools) the same way.

One reference of behavior is dockta.

For example this DESCRIPTION file

https://github.com/chainsawriot/mzesalike/blob/master/DESCRIPTION

should give: cran::leaflet, github::yihui/xaringan, github::chainsawriot/xaringanExtra, github::chainsawriot/xaringanExtra. If there is a Date field, we can use it as snapshot_date.

I'm still thinking about how export_description should behave. We can either write the entire installation_order (like export_renv) or just the initial queried pkgrefs (that would be like dockta).

[schochastics]

Ok I will start working on as_pkgrefs("DESCRIPTION") for now