1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239
|
---
title: "ZIP file structures"
output: github_document
---
```{r setup, include=FALSE}
knitr::opts_chunk$set(comment = "#>", collapse = TRUE)
```
```{r}
devtools::load_all("~/rrr/usethis")
library(fs)
```
## Different styles of ZIP file
usethis has an unexported function `tidy_unzip()`, which is used under the hood in `use_course()` and `use_zip()`.
It is a wrapper around `utils::unzip()` that uses some heuristics to choose a good value for `exdir`, which is the "the directory to extract files to."
Why do we do this?
Because it's really easy to _not_ get the desired result when unpacking a ZIP archive.
Common aggravations:
* Instead of the unpacked files being corraled within a folder, they explode as "loose parts" into the current working directory. Too little nesting.
* The unpacked files are contained in a folder, but that folder itself is contained inside another folder. Too much nesting.
`tidy_unzip()` tries to get the nesting just right.
Why doesn't unzipping "just work"?
Because the people who make `.zip` files make lots of different choices when they actually create the archive and these details aren't baked in, i.e. a successful roundtrip isn't automatic.
It usually requires some peeking inside the archive and adjusting the unpack options.
This README documents specific `.zip` situations that we anticipate.
## Explicit parent folder
Consider the foo folder:
```{bash}
tree foo
```
Zip it up like so:
```{bash, eval = FALSE}
zip -r foo-explicit-parent.zip foo/
```
This is the type of ZIP file that we get from GitHub via links of the forms <https://github.com/r-lib/usethis/archive/main.zip> and <http://github.com/r-lib/usethis/zipball/main/>.
Inspect it in the shell:
```{bash}
unzip -Z1 foo-explicit-parent.zip
```
Or from R:
```{r}
foo_files <- unzip("foo-explicit-parent.zip", list = TRUE)
with(
foo_files,
data.frame(Name = Name, dirname = path_dir(Name), basename = path_file(Name))
)
```
Note that the folder `foo/` is explicitly included and all of the files are contained in it (in this case, just one file).
## Implicit parent folder
Consider the foo folder:
```{bash}
tree foo
```
Zip it up like so:
```{bash, eval = FALSE}
zip -r foo-implicit-parent.zip foo/*
```
Note the use of `foo/*`, as opposed to `foo` or `foo/`.
This type of ZIP file was reported in <https://github.com/r-lib/usethis/issues/1961>.
The example given there is <https://agdatacommons.nal.usda.gov/ndownloader/files/44576230>.
Inspect our small example in the shell:
```{bash}
unzip -Z1 foo-implicit-parent.zip
```
Or from R:
```{r}
foo_files <- unzip("foo-implicit-parent.zip", list = TRUE)
with(
foo_files,
data.frame(Name = Name, dirname = path_dir(Name), basename = path_file(Name))
)
```
Note that `foo/` is not included and its (original) existence is just implicit in the relative path to, e.g.,
`foo/file.txt`.
Here's a similar look at the example from issue #1961:
```bash
~/rrr/usethis/tests/testthat/ref % unzip -l ~/Downloads/Species\ v2.3.zip
Archive: /Users/jenny/Downloads/Species v2.3.zip
Length Date Time Name
--------- ---------- ----- ----
1241 04-27-2023 09:16 species_v2/label_encoder.txt
175187560 04-06-2023 15:13 species_v2/model_arch.pt
174953575 04-14-2023 12:28 species_v2/model_weights.pth
--------- -------
350142376 3 files
```
Note also that the implicit parent folder `species_v2` is not the base of the ZIP file name `Species v2.3.zip`.
## No parent
Consider the foo folder:
```{bash}
tree foo
```
Zip it up like so:
```{bash, eval = FALSE}
(cd foo && zip -r ../foo-no-parent.zip .)
```
Note that we are zipping everything in a folder from *inside* the folder.
Inspect our small example in the shell:
```{bash}
unzip -Z1 foo-no-parent.zip
```
Or from R:
```{r}
foo_files <- unzip("foo-no-parent.zip", list = TRUE)
with(
foo_files,
data.frame(Name = Name, dirname = path_dir(Name), basename = path_file(Name))
)
```
All the files are packaged in the ZIP archive as "loose parts", i.e. there is no explicit or implicit top-level directory.
## No parent, the DropBox Variation
This is the structure of ZIP files yielded by DropBox via links of this form <https://www.dropbox.com/sh/12345abcde/6789wxyz?dl=1>. I can't figure out how to even do this with zip locally, so I had to create an example on DropBox and download it. Jim Hester reports it is possible with `archive::archive_write_files()`.
<https://www.dropbox.com/sh/5qfvssimxf2ja58/AABz3zrpf-iPYgvQCgyjCVdKa?dl=1>
It's basically like the "no parent" example above, except it includes a spurious top-level directory `"/"`.
Inspect our small example in the shell:
```{bash}
unzip -Z1 foo-loose-dropbox.zip
```
Or from R:
```{r}
# curl::curl_download(
# "https://www.dropbox.com/sh/5qfvssimxf2ja58/AABz3zrpf-iPYgvQCgyjCVdKa?dl=1",
# destfile = "foo-loose-dropbox.zip"
# )
foo_files <- unzip("foo-loose-dropbox.zip", list = TRUE)
with(
foo_files,
data.frame(Name = Name, dirname = path_dir(Name), basename = path_file(Name))
)
```
Also note that, when unzipping with `unzip` in the shell, you get this result:
```
Archive: foo-loose-dropbox.zip
warning: stripped absolute path spec from /
mapname: conversion of failed
inflating: file.txt
```
which indicates some tripping over the `/`.
Only `file.txt` is left behind.
This is a pretty odd ZIP packing strategy. But we need to plan for it.
## Only subdirectories
For testing purposes, we also want an example where all the files are inside subdirectories.
Examples based on the yo directory here:
```{bash}
tree yo
```
Zip it up, in all the usual ways:
```{bash, eval = FALSE}
zip -r yo-explicit-parent.zip yo/
zip -r yo-implicit-parent.zip yo/*
(cd yo && zip -r ../yo-no-parent.zip .)
```
Again, I couldn't create the DropBox variant locally, so I did it by downloading from DropBox.
```{r eval = FALSE}
# curl::curl_download(
# "https://www.dropbox.com/sh/afydxe6pkpz8v6m/AADHbMZAaW3IQ8zppH9mjNsga?dl=1",
# destfile = "yo-loose-dropbox.zip"
# )
```
Inspect each in the shell:
```{bash}
unzip -Z1 yo-explicit-parent.zip
```
```{bash}
unzip -Z1 yo-implicit-parent.zip
```
```{bash}
unzip -Z1 yo-no-parent.zip
```
```{bash}
unzip -Z1 yo-loose-dropbox.zip
```
|