On 01/28/2010 06:23 PM, Pierre Schmitz wrote:
Am Sonntag, 17. Januar 2010 17:27:57 schrieb Pierre Schmitz:
Hi all,
recently I have seen that there were a lot of commits introducing versioned deps down to the pkgrel level. I think we should avoid such deps if possible. There are possibly only some important packages in core where this is useful and in such cases you should add not only an lower but upper bound (see kernel modules for example).
For anything else this is not needed (at least for Arch), adds more complexity or simply breaks stuff. For more detailed arguments please read at least the first three messages in http://mailman.archlinux.org/mailman/private/arch-dev/2009-October/011439.h tml
This is just a general reminder and I did not intend to attack anyone. So just keep it simple. :-)
Greetings,
Pierre
What do you think if we work on some kind of policy that recommends strict versioned deps for packages in the base group and none for everything else?
-1
This way we could avoid any major damage (caused by users, mirror problems or even our fault) but on the other hand does not introduce complexity and other problems for non-base packages.
i think in this way we will have major breakage. For example: http://bugs.archlinux.org/task/18051 if bash had an extended version on readline dependency he wouldn't trash his system. The examples can be a lot. External modules(which are in extra) they have kernel26>=2.6.32 kernel26<2.6.33 just to avoid breakage. -- Ionut