rpm-ostree pull 🖧 #713
Labels
Comments
Closed
|
See also related discussion for the rpmmd side in #1035. |
|
I'm thinking now this should just be a |
jlebon
added a commit
to jlebon/rpm-ostree
that referenced
this issue
Oct 10, 2017
To complement the new `--cache-only` option, add a `--download-only` option. This does exactly what it says: we download the ostree, download and import packages, but don't actually commit & deploy. This can be used to effectively prime a follow-up `--cache-only` operation that can be done during a more convenient/safer maintenance window. I debated naming the two options `--pull-only` and `--deploy-only` like the ostree equivalents. Though "pull" felt like the wrong word given that it's associated more with ostree pulling but rpm-ostree also downloads & imports RPMs. As for `--deploy-only` vs `--cache-only`, it seems like `--cache-only` is a more accurate description of the functionality (i.e. rather than describing an action, it describes a mode). I also considered `--no-download` to make the synergy with `--download-only` more obvious. Maybe that's better? Naming is hard... Closes: coreos#713
jlebon
added a commit
to jlebon/rpm-ostree
that referenced
this issue
Oct 12, 2017
To complement the new `--cache-only` option, add a `--download-only` option. This does exactly what it says: we download the ostree, download and import packages, but don't actually commit & deploy. This can be used to effectively prime a follow-up `--cache-only` operation that can be done during a more convenient/safer maintenance window. I debated naming the two options `--pull-only` and `--deploy-only` like the ostree equivalents. Though "pull" felt like the wrong word given that it's associated more with ostree pulling but rpm-ostree also downloads & imports RPMs. As for `--deploy-only` vs `--cache-only`, it seems like `--cache-only` is a more accurate description of the functionality (i.e. rather than describing an action, it describes a mode). I also considered `--no-download` to make the synergy with `--download-only` more obvious. Maybe that's better? Naming is hard... Closes: coreos#713
jlebon
added a commit
to jlebon/rpm-ostree
that referenced
this issue
Oct 13, 2017
To complement the new `--cache-only` option, add a `--download-only` option. This does exactly what it says: we download the ostree, download and import packages, but don't actually commit & deploy. This can be used to effectively prime a follow-up `--cache-only` operation that can be done during a more convenient/safer maintenance window. I debated naming the two options `--pull-only` and `--deploy-only` like the ostree equivalents. Though "pull" felt like the wrong word given that it's associated more with ostree pulling but rpm-ostree also downloads & imports RPMs. As for `--deploy-only` vs `--cache-only`, it seems like `--cache-only` is a more accurate description of the functionality (i.e. rather than describing an action, it describes a mode). I also considered `--no-download` to make the synergy with `--download-only` more obvious. Maybe that's better? Naming is hard... Closes: coreos#713
jlebon
added a commit
to jlebon/rpm-ostree
that referenced
this issue
Oct 13, 2017
To complement the new `--cache-only` option, add a `--download-only` option. This does exactly what it says: we download the ostree, download and import packages, but don't actually commit & deploy. This can be used to effectively prime a follow-up `--cache-only` operation that can be done during a more convenient/safer maintenance window. I debated naming the two options `--pull-only` and `--deploy-only` like the ostree equivalents. Though "pull" felt like the wrong word given that it's associated more with ostree pulling but rpm-ostree also downloads & imports RPMs. As for `--deploy-only` vs `--cache-only`, it seems like `--cache-only` is a more accurate description of the functionality (i.e. rather than describing an action, it describes a mode). I also considered `--no-download` to make the synergy with `--download-only` more obvious. Maybe that's better? Naming is hard... Closes: coreos#713
jlebon
added a commit
to jlebon/rpm-ostree
that referenced
this issue
Oct 13, 2017
To complement the new `--cache-only` option, add a `--download-only` option. This does exactly what it says: we download the ostree, download and import packages, but don't actually commit & deploy. This can be used to effectively prime a follow-up `--cache-only` operation that can be done during a more convenient/safer maintenance window. I debated naming the two options `--pull-only` and `--deploy-only` like the ostree equivalents. Though "pull" felt like the wrong word given that it's associated more with ostree pulling but rpm-ostree also downloads & imports RPMs. As for `--deploy-only` vs `--cache-only`, it seems like `--cache-only` is a more accurate description of the functionality (i.e. rather than describing an action, it describes a mode). I also considered `--no-download` to make the synergy with `--download-only` more obvious. Maybe that's better? Naming is hard... Closes: coreos#713
jlebon
added a commit
to jlebon/rpm-ostree
that referenced
this issue
Oct 16, 2017
To complement the new `--cache-only` option, add a `--download-only` option. This does exactly what it says: we download the ostree, download and import packages, but don't actually commit & deploy. This can be used to effectively prime a follow-up `--cache-only` operation that can be done during a more convenient/safer maintenance window. I debated naming the two options `--pull-only` and `--deploy-only` like the ostree equivalents. Though "pull" felt like the wrong word given that it's associated more with ostree pulling but rpm-ostree also downloads & imports RPMs. As for `--deploy-only` vs `--cache-only`, it seems like `--cache-only` is a more accurate description of the functionality (i.e. rather than describing an action, it describes a mode). I also considered `--no-download` to make the synergy with `--download-only` more obvious. Maybe that's better? Naming is hard... Closes: coreos#713
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See #639
as well as ostreedev/ostree#642
rpm-ostree pullshould be likeostree pull $baseref+ "download and import new updated packages". The first part is trivial, the second part requires reworking our package import GC to have some notion of a "pulled deployment".The text was updated successfully, but these errors were encountered: