I was informed that binaries where promised with new build system. This is an unreasonable request for a team of 1. 3 Platforms and many packaging systems for Linux would create an endless packaging process. I know how much work Harold does just keeping up with Kubuntu binaries.. If teams want to create binaries with artifacts we can discuss publishing those to somewhere.
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Restricted Maniphest Task | ||||
| Resolved | scarlettclark | T232 Provide binaries |
Comment Actions
Also one has to say that the CI system requires a very specific setup w.r.t. to environment, tests and whatnot.
Though, admittedly, it would be nice to have this functionality, but that'd need much more manpower!
Comment Actions
Just some clarity here: We will not be doing distribution independent binaries. Ever. Distributions have much more in so far as resources to handle this themselves.
Possibly appstreamer for Linux?
OSX and Windows binaries really should be done by us.
Comment Actions
This would be preferable to the Emerge system. It seems a lot of duplicated effort to have binaries only available through Emerge, and it would be nice to have someone doing a continuous build. I think the bandwidth difference providing binaries vs. source are pretty minor too, since the current offering means cloning a whole Git repo. The Frameworks sources on my computer occupy over 700MB, and the compiled libraries (dlls plus .libs) are under 100MB.
Comment Actions
We have decided we will provide binaries for Windows and OSX only, distributions can handle linux binaries as they have more resources available.
Comment Actions
The binaries the CI system produces can be freely downloaded by anyone from https://build-artifacts.kde.org/ and the tooling in the ci-tooling repository can assist with resolving dependencies, downloading those and unpacking them as needed.
Whether you'll be able to use them is another issue as they're made to fit the environment that created them though.