Yeah but shouldn’t the order matter? My understanding was that && just said 'after the previous command, run this… ’ so running upgrade before update would miss any changes changes to repos… From what I can tell update is required before upgrade (just like you have it), doing it in reverse missed a ton of updates for me.
Presumably running upgrade with the update flag is smart enough to do it in the proper order because there would be no point in doing it in the opposite order. Many other package managers just work like this out of the box. Homebrew is such an example. Running upgrade automatically does “update” first.
Yeah but shouldn’t the order matter? My understanding was that && just said 'after the previous command, run this… ’ so running upgrade before update would miss any changes changes to repos… From what I can tell update is required before upgrade (just like you have it), doing it in reverse missed a ton of updates for me.
Presumably running upgrade with the update flag is smart enough to do it in the proper order because there would be no point in doing it in the opposite order. Many other package managers just work like this out of the box. Homebrew is such an example. Running upgrade automatically does “update” first.
If it were upgrade && update, yes that would miss the boat. --update is a baked in feature of apt upgrade, so it knows what to do ^_^