On Thu, Jun 8, 2017 at 10:49 PM, Randy Barlow <firstname.lastname@example.org> wrote:
On Thu, 2017-06-08 at 22:17 +0200, Adam Samalik wrote:
> You add the package and other people start to use it. That's great
> until you need to change the version, but can't, because other people
> started to use it as a dependency and it would break their stuff.
I recently heard that it will be impossible to install two packages
that depend on different versions of a dependency at the same time. For
example, if package A depends on C < 2.0 and package B depends on C >=
2.0, it will be impossible to install A and B on the same system. Is
this true? If so, I worry that we will see fracturing in Fedora as
packages drift apart in their dependencies. If not so, I apologize for
the noise ☺
I would say it's "half truth" right now. :-)
There has been no extra work on changing RPMs. If something conflicts now, it will keep conflicting. But!
Actually, I think the Modularity work can (potentially) provide a solution for installing multiple versions of the same package for RPM (assuming that the packages are properly packaged so that different versions don't conflict with each other, e.g. two versions of a library like boost).
So, not everything will probably be installable as RPMs on the same system at the same time. But I see the world is going to containers, and I'm thinking if not being to install all RPMs next to each other on a single system is still a real problem. Thoughts?