On 20 June 2016 at 10:03, Dave Plater <davejpla...@gmail.com> wrote: > This thread has the wrong subject. > I think this is a proposal for a new Packman model. > Rolling release Packman and stable Packman,
While I support this idea, I still think packman needs to stop rolling faster than Tumbleweed Therefore for rolling packman, I still recommend it should be built against Tumbleweed, and not an untested devel project. So while the discussions about Leap go on in the other thread, this new thread is to discuss the situation specific to Tumbleweed Tumbleweed is a tested rolling distribution. While it can change anything at any time, it only changes stuff once they are tested and integrated. Packman's current model for Tumbleweed, building against multimedia:libs and not Tumbleweed, means that Packman users get packages of the NEXT version of ffmpeg, gstreamer, etc, BEFORE it is ready for Tumbleweed This causes disruption, pain, heartache, and I've now lost track of the amount of times it's broken GNOME applications that used gstreamer. Packman is effectively treating it's users like guineapigs for the unreleased packages in multimedia:libs. I'd rather Packman be a reliable source of packages that can be trusted. Please build Packman for Tumbleweed using linked packages from Tumbleweed. Also, Bjorn's advice about =direct is still good ;) - Richard _______________________________________________ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman