You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mpfr is never built as a "main target" but (almost always) as a dependency of (different versions of) gcc builds.
It would be useful to list the "main pkg" and "main pkg ver" to get a better overview in which context a dependency was built.
The data could currently be viewed via: $ butido db submit d1cbd532-e400-4c1a-bbc6-074f80ddd538
But this way is tedious for multiple builds.
To be consistent with the other column names we might also switch from "Package" to "pkg" and from "Version" to "ver".
Also all header entries might as well be in lower case.
The new headers would be "main pkg" and "main pkg ver".
The text was updated successfully, but these errors were encountered:
currently the output of
butido db jobs -p mpfr -L 5
looks like thismpfr is never built as a "main target" but (almost always) as a dependency of (different versions of) gcc builds.
It would be useful to list the "main pkg" and "main pkg ver" to get a better overview in which context a dependency was built.
The data could currently be viewed via:
$ butido db submit d1cbd532-e400-4c1a-bbc6-074f80ddd538
But this way is tedious for multiple builds.
To be consistent with the other column names we might also switch from "Package" to "pkg" and from "Version" to "ver".
Also all header entries might as well be in lower case.
The new headers would be "main pkg" and "main pkg ver".
The text was updated successfully, but these errors were encountered: