The developers of most software won't do this. Most likely they don't even know what repositries they need to add for each
I think there are enough possibilities for its use within the opensuse community to make it worthwhile by themselves. If it became popular more people would start using it.
So now I have to find out what repositories I must point people to for each version of SUSE. Naturaly this should then also be done for other distributions. Technicaly doable. In reality it won't work.
For packages in the build service at least it should be completely automatable, and for anyone it should be relatively trivial compared to the difficulty of packing
If you see how many deveopers only give you a sourcefile or just sourcefile and a *.deb, I doubt very much that they suddenly will start adding what you want.
Indeed, I wasn't suggesting that everyone would suddenly start using it overnight. I fail to see any downsides though, and it would solve a problem for users even if only adopted by current community members. However, should it be popular and adopted by others it could help far more.
The void is filled by repositories. The SUSE Build Server should be able to fill that void.
Indeed, but not everything can be hosted by this, both from practical and legal limitations. Something like I suggested would enable online software catalogues like http://klik.atekon.de/ and linspire's click n run for suse packages. - You agree it is technically possible. - There are projects that could immediately benefit from something such as this. - If this were available it /could/ be adopted by many (if it's not it can't) Expecting users to deal with adding additional repositories or even to understand what they are is not acceptable imho. What I think would be better to discuss are whether a) Is this technically feasible? b) Could it make things better for users Benjamin Weber