> It is not the users you need to convince. It is the thousands of people > who make the software and might not even use SUSE that you need to > convince. Remember that many of them can't even bother to make an RPM > package.
As I already said I believe something along these lines would be useful to users even if only used in conjunction with the build service and existing suse packaging projects. It would of course be even more beneficial if many people used it, but there is no way of knowing whether anyone would adopt it. I have pointed you at projects that have done similar things and been very successful, yet you still think it is unworkable. I suggested a solution to the problem that does exist of users downloading individual packages and not being able to install them. This may not be the best way of going about solving the problem but the problem does exist, and to users of other systems it makes package management seem worse than what they are used to. Prior to the mess in 10.1 the vast majority of the questions in #suse were how to add package repositories (often the user doesn't even understand why they need to), and how to install things like mp3 support, or win32codecs etc. Since january in #suse alone 761 people have needed to know how to add package repositories and, 568 people have asked how to install mp3 support. Do you have any ideas of alternative ways in which this problem might be solved, which doesn't involve users having to learn what repositories are and how to add them. Benjamin Weber --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
