Le mercredi 05 juillet 2006 à 22:09 +0200, Enrico Scholz a écrit : > ville.skytta@xxxxxx (Ville Skyttä) writes: > > >> Because the Fedora Extras packages are for a specific environment > >> (FE4, FE5, devel) only, you can be sure that the needed program > >> versions are available there and the explicit version is not needed. This is totally wrong. When you package for FCx, and one of your deps got a major version bump in FCx updates, what do you target ? FCx as it was released of FCx after all updates are applied ? How do you tell the package manager when your package is safe to use ? (this is actually worse for 3rd party repositories which target 5-years-long RHEL) Also note that since the project allows parallel updates in all FE releases (instead of freezing everything but devel),depending on the yum invocation order people will have vastly different package versions on their systems (within a single FE release). Not dangerous for people who do daily broadband pulls. But deadly for systems only used every few/weeks, and synced every few months (think computer at your grandma or vacation house, small server only updated when there is a problem, etc) Unversionned deps, when you know at which version boundary your package breaks, is just playing with fire. -- Nicolas Mailhot
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
-- Fedora-packaging mailing list Fedora-packaging@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-packaging
