"Stefan Br�����������������������������������" wrote:
In this case, not a good idea (languag_e_s), but come on, it is much do difficult to go to download.opensuse.org or to the OBS to check how a project/package is exactly named. Hey, that would require using ones brain, which is hardly possible if it is totally exhausted by ranting all the time ...
--- It might require that someone actually tried building it when they said they did, so a cut-paste from their terminal into email wouldn't end up with errors. If nobody even knows the syntax or where it is located to try, then how is it that we know it works? It is awfully exhausting for me to file a bug report on it not working, then be told it works, with the proof being something I can't replicate. I never had a problem building packages when they were built on a normal suse system. Only since osc was added have I found things often don't build correctly on a normal system. When developers of packages ship their source, they don't ship rpm's built in a clean-room. They most often ship some configuration detection based make system that works across a number of platforms. Since the introduction of OSC, building has gotten very difficult. One example of bad practice -- in core utils, they copy patches, on source install, into a patch dir -- but they don't clear out that dir first. The the build does a "for i in (patch/*.*);do..." Which causes failures if you have built 2 different versions of coreutils in a row. Meanwhile, neither path to the perl package seems to work. :-( -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org