GNOME Bugzilla – Bug 711870
Daily GStreamer SDK Git Builds
Last modified: 2018-05-04 09:51:32 UTC
I provide daily GStreamer SDK builds of the SDK on my website: http://gstreamer.zeranoe.com/builds/ I am wondering if it would be possible to get a link on GStramer's website thank links to these builds? The builds are compiled using the latest git versions of all gstreamer components. They are cross compiled on Debian and packaged on Windows. I think the build would be very helpful for Windows developers, and would really help to bring GStreamer to new users.
While I think it's a good idea to add it to the main website, you can also add it yourself to the oft-neglected wiki here: http://gstreamer.freedesktop.org/wiki Also, I've noticed that "gstreamer daily builds" returns your site in the first ten entries on Bing, Google, and Yahoo. Thanks for your work by the way, very useful.
The wiki is no longer functional, it was disabled by fdo admins after some DoS/spam episode. We need to clean that up, keep the good bits and remove the rest one of these days. As for daily builds, I think that's great, and if you saw my talk at the gstreamer conference you'll know that it's something I definitely want. However, I also think that this is something we should be providing ourselves using our own servers/resources (which was already planned). I think it's a matter of 'trust' and of 'branding' for lack of better words. The GStreamer website should be where people get their binaries from, and the should be generated by us. Linking to yet another website is just going to add more confusion, the situation is confusing enough already with the .com situation.
Many other open source projects link to other websites for binaries of their software. I don't think it would confuse the users, and if they are seeking out an the SDK I think it's safe to assume a certain level of compliance. I believe users will find these builds helpful, so until GStreamer starts compiling their own SDKs, why not link these? If I have already put in the work and continue to on a daily basis, it seems silly to reinvent the wheel just to have them locally hosted.
Server doesn't exist anymore. It's on our long-term plan for CI and gitlab switching. Closing.