On 11/24/2017 9:41 AM, Christian Betz wrote:
First, a potential non-answer: Use containers. Or Flatpak. CL
this is in part a real answer. some things are really done better as a container
or a flatpak.... not everything of course.
(a) you have some device that can run clear linux and you want to package
your own stuff on it to make an "appliance" which can be remotely updated
using swupd. for something concrete: imagine i wanted to make and brand a
digital signage controller based on intel NUCs. it should magically update
itself with my branded software by contacting a swupd server that I host.
as we're expanding our focus a bit in the IOT kind of space (big IOT, not
this indeed one of our models
and mixer is exactly for these kind of scenarios; be it a device maker for their own
devices, or a SRE team for a datacenter managing a set of systems, mixer is how
you get full control, not just of what you add, but also when and how and what you update
BTW: CL specifically uses something called 'autospec' to
files for RPM builds more easily (see:
AFAICT not all CL packages are generated using autospec; in other words I
don't think you *have* to use autospec but you are encouraged to.
autospec for us is targeted for "95%", the packages that have sane (well,
lets not debate if autoconf or cmake or .. are sane or insane) build systems.
In addition, autospec is basically our packaging standard; it's code not english, but
the way autospec puts down packages is by construction how we want to package.
(c) you are a developer of some product or open source project and you want
to make available for purchase/download your application for clear linux
(i.e. for other users of clear linux). In a "classic distro" model you
might make available deb or RPM packages for popular distros. Or better:
you have repos for yum/app. But what should you do for users of Clear
Linux? If you cannot or don't want the CL team to officially adopt your
package? I cannot answer this one :(
if we miss open source stuff, just ask for it to be included, by means
of an URL to the release tar file....
if it just autospecs and it's not insane in terms of the legal/security side,
just add it.
(rule of thumb: if it's good enough for fedora and debian it's likely not insane)