Printed text during package installing/updates

Internals & Design
1

I have noticed after updating to 1.6.0 that I sometimes get something like the following printed during package-installation/updating:

    Updating registry at `C:\Users\densb\.julia\registries\General`
    Updating git-repo `https://github.com/JuliaRegistries/General.git`
   Resolving package versions...
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Project.toml`
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Manifest.toml`
   Resolving package versions...
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Project.toml`
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Manifest.toml`
   Resolving package versions...
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Project.toml`
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Manifest.toml`
   Resolving package versions...
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Project.toml`
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Manifest.toml`
   Resolving package versions...
    Updating `C:\Users\densb\.julia\environments\v1.6\Project.toml`
  [916415d5] + Images v0.23.3
    Updating `C:\Users\densb\.julia\environments\v1.6\Manifest.toml`

I believe that this occurs during the little dance to figure out package compatibility, and which latest version of each package results in a compatible set. As a user, however, it does appear as if the installation process is stuck.

Are there better ways to print this?

2

Even after having run the installation once, so that I know that all packages fresh and up to date, i got stuck in this dance for quite a few rounds when running again:

    Updating registry at `C:\Users\densb\.julia\registries\General`
    Updating git-repo `https://github.com/JuliaRegistries/General.git`
   Resolving package versions...
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Project.toml`
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Manifest.toml`
   Resolving package versions...
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Project.toml`
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Manifest.toml`
   Resolving package versions...
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Project.toml`
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Manifest.toml`
   Resolving package versions...
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Project.toml`
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Manifest.toml`
   Resolving package versions...
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Project.toml`
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Manifest.toml`
   Resolving package versions...
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Project.toml`
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Manifest.toml`
   Resolving package versions...
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Project.toml`
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Manifest.toml`
   Resolving package versions...
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Project.toml`
  No Changes to `C:\Users\densb\.julia\environments\v1.6\Manifest.toml`

Not the most user-friendly output.

For completeness, the installation commands that triggered this are:

using Pkg
Pkg.add.(["Pluto", "PlutoUI", "CairoMakie", "XLSX", "Images", "FileIO", "DataFrames", "PackageCompiler"])
3

You broadcast Pkg.add over the vector so you call Pkg.add over and over again, and every call generate that output.

3 Likes
4

That makes a lot of sense! So the solution is simply to not broadcast, because the function can take a vector of string directly?

5

Yes.

6

It seems obvious when looking seeting a method of Pkg.add for a vector of strings. I feel like at some point I found it to be nessecary, but I must have misunderstood something back then. In any case, thanks for the quick and clear reply!