[opensuse-project] project dependencies
Hi folks, I was just bitten again by project dependencies: openSUSE:Tools depends on ruby to get more current packages than what we had on sle10. I don't want to copy in the packages fromt heruby project and I don't want to sourcelink them. I instead want the ruby project to 'know' that there are other projects depending on it, so they get a message if they try to disable the sle10 project repo. And what I actually want is to design and document a best practice how projetcs should interact in the software integration process, how project releases are done, so you can rely on another project without copying or linking it's base packages in. S. -- Susanne Oberhauser +49-911-74053-574 SUSE -- a Novell Business OPS Engineering Maxfeldstraße 5 Processes and Infrastructure Nürnberg SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Wednesday 03 Dec 2008, Susanne Oberhauser wrote:
I don't want to copy in the packages fromt heruby project and I don't want to sourcelink them. I instead want the ruby project to 'know' that there are other projects depending on it, so they get a message if they try to disable the sle10 project repo.
And what I actually want is to design and document a best practice how projetcs should interact in the software integration process, how project releases are done, so you can rely on another project without copying or linking it's base packages in.
Can I suggest that projects have explicitly, as part of their definition, the projects on which they depend / are built. That would allow the package dependency trees to start with a repo dependency tree. I have had different problems where two projects included new (and incompatible) versions of a package in the base system. There were no warning about the impending breakage, and it took a lot of work to unwind. David -- D Hodgson P: 020 71 833 722 M: 07984 069 846 F: 0845 86 75 74 1 E: david@different-perspectives.com -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Administrator
Can I suggest that projects have explicitly, as part of their definition, the projects on which they depend / are built. That would allow the package dependency trees to start with a repo dependency tree. I have had different problems where two projects included new (and incompatible) versions of a package in the base system. There were no warning about the impending breakage, and it took a lot of work to unwind.
You don't mean osc meta prj openSUSE:Tools do you? What I'd like to see is - an error message if you disable a repo that's needed by another project, --force overridable - a tool that takes generates a graph of repo dependencies and package dependencies, usable with tools like cytoscape http://www.cytoscape.org so you can browse package and repo dependencies S. -- Susanne Oberhauser +49-911-74053-574 SUSE -- a Novell Business OPS Engineering Maxfeldstraße 5 Processes and Infrastructure Nürnberg SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
participants (2)
-
Administrator -
Susanne Oberhauser