* Rémi Cardona <[EMAIL PROTECTED]> schrieb: > Best example on how to do that is gstreamer. All the plugins come in 3 > tarballs but each can be built individually. Really clean.
ACK. That's how it always should be. All my own packages also work this way - ev'ry thing else doesnt get released ;-P > >If the upstream really blocks it, do a > >fork / maintain a patchline (like OSS-QM project does). > > > >I'm already doing so with several packages. > > I've seen you talk about that project before but I don't feel > comfortable going down that road. We want to work with upstream > and let them know what our needs are. Maintaining patches is a > lot of work and forking is even more work. Right. Therefore OSS-QM is meant as just an intermedia step. To form a bridge between (virtually all) distros and upstream. Sometimes the upstream has even valid reasons for not having distro's or embedded needs as high priority, eg. if their primary goal are new features - many upstream folks are coding ONLY just for fun and simply don't want to care about stability. In those cases we simply should let them pass and avoid unnecessary conflicts. In fact we (as OSS-QM) would then maintain the stable branch, while the upstream is just the devel branch. Maybe you remember the discussions about stable vs. dev kernel branches: the kernel folks wanted to give up stable branches, leaving them to the individual distros and concentrate just on devel branch. A lot of people were totally unhappy with this idea, so they abondened the idea. Otherwise the kernel would have been the killer job for an project like OSS-QM. > Even though I'm still a relatively young Gentoo dev (only been > here for 1.5 years), I have yet to see upstream projects reject > build patches that make our lives easier. Yeah, I've experienced this a lot of times and learned that it doesn't make sense trying to convice people to things they simply do not want. So I founded OSS-QM as an proxy/overlay project with the primary goals: reacting ASAP, providing things the distros need in an *generic* way, but not developing new features. The upstream gets announced about patches, but doesn't get penetrated with things they're obviously not interested in. cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service - http://www.metux.de/ --------------------------------------------------------------------- Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ --------------------------------------------------------------------- -- gentoo-dev@lists.gentoo.org mailing list
