Alexey Eremenko wrote:
Wasn't the original plan to package 'useful utilities' or something among these lines? Now adding this old compiler just to be able to compile a package written in historic C++ (didn't we talk about maintainability / upstream support?), this old library because another project didn't catch up with api changes (likewise), this new library because this cool app unfortunately requires features only found in svn HEAD of said library - where does this stop? I'm affraid that without a hard rule of not duplicating packages from the distro, the new repository won't be much different from existing repos (and I'm not sure I would still want to participate in that).
Hmmm... So you believe this is absolutely evil ?
Not 'absolutely evil' but it can cause trouble (trust me - e.g. we had enough fun in devel:laguages:python with python-curl requiring newer curl and newer curl replacing old curl required by rest of the system on older distros). I was hoping for a repository without these problems, which could be safely added as installation source without having to disable all the time. IMO, in 90% of the cases where some package needs a newer/older version, someone just needs to sit down and port the package to the distro. The remaining 10% could then be handled case by case. And yes, so far I'm interested and I listed myself on your draft page :) Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org