[yast-devel] openSUSE 11.0 - Splitting YaST packages - Call for help
Hi YaSTies, I've found (and I'm probably not alone), that RPM dependencies in YaST packages might cause cyclic/cross dependencies, sometimes even when building the packages. In the past, we were solving such issues by moving the YCP/Perl module, that was needed by two or more YaST RPMs, to yast2.rpm package. However, this seems to be something that can't last forever ;) The current yast2.rpm package is already quite big. I already did something similar for 10.2 but YaST is currently widely open and plenty of developers are familiar with YaST internal processes so it's not needed to be a one-man-show ;). My idea is simple: * First, check the current dependencies. Can't we just remove them? * Then, think about moving some shared code/modules to some RPM that is already requested by those which need to share it. * Think about splitting yast2.rpm into more packages (several YaST RPMs don't need all that stuff). * Splitting yast2-installation into two packages. * Some debugging tools or scripts would be helpful. What should we achieve? * Less dependencies * No more cyclic issues Of course, some dependencies need a longer discussion, some don't need to be expressed at all (for inst-sys, for instance). #yast IRC channel at Freenode seems to be very-well suitable for such discussion ;) So, who's interested in it :)? I am, of course :) Have a nice day Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic
Is it possible that we create some kind of provides and requires extractor for rpm just like there are for .so files, for perl, for mono, etc. rpm -q --requires mono-winforms mono(Mono.Posix) = 1.0.5000.0 mono(Mono.Posix) = 2.0.0.0 mono(System) = 1.0.5000.0 mono(System) = 2.0.0.0 mono(System.Configuration) = 2.0.0.0 So YaST modules could be scanned for provides and requires, and rpm dependencies set automatically: YaST(Storage) == 1.3 or something like that. That would prevent manual package requires that are outdated, sometimes not needed, sometimes missing, etc? Duncan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Mon, Oct 29, 2007 at 11:21:04AM +0100, Lukas Ocilka wrote:
What should we achieve? * Less dependencies * No more cyclic issues
OK. What are the offending dependencies? Do we have a list somewhere (in autobuild?) that we can pull out to the light? -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
* Martin Vidner <mvidner@suse.cz> [Oct 29. 2007 11:30]:
On Mon, Oct 29, 2007 at 11:21:04AM +0100, Lukas Ocilka wrote:
What should we achieve? * Less dependencies * No more cyclic issues
OK. What are the offending dependencies? Do we have a list somewhere (in autobuild?) that we can pull out to the light?
'repotools' in zypp svn have a way to create .dot (for graphiz) files visualizing the dependencies. Running this for each yast package should give an initial impression. Klaus -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Monday 29 October 2007 12:20:54 Klaus Kaempf wrote:
* Martin Vidner <mvidner@suse.cz> [Oct 29. 2007 11:30]:
On Mon, Oct 29, 2007 at 11:21:04AM +0100, Lukas Ocilka wrote:
What should we achieve? * Less dependencies * No more cyclic issues
OK. What are the offending dependencies? Do we have a list somewhere (in autobuild?) that we can pull out to the light?
'repotools' in zypp svn have a way to create .dot (for graphiz) files visualizing the dependencies.
repotools is in really bad state and did not work for me last time I tried to graph something. I have a ton of changes (includinga cmd line client, and others) in my local repo, but I am demotivated to work more on it until I have time to create testcases for all the code. I would recommend using YaST to create a solver testcase of installing yast, and use schubi's solver widget in the testcase Duncan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Martin Vidner napsal(a):
On Mon, Oct 29, 2007 at 11:21:04AM +0100, Lukas Ocilka wrote:
What should we achieve? * Less dependencies * No more cyclic issues
OK. What are the offending dependencies? Do we have a list somewhere (in autobuild?) that we can pull out to the light?
Coolo, Rudi, could you, please, send us the list of YaST-related packages that are in a cyclic build-loop? Or just any other similar problem? We have such list, right? Thanks a lot! Lukas
On Mon, 29 Oct 2007, Lukas Ocilka wrote:
Martin Vidner napsal(a):
On Mon, Oct 29, 2007 at 11:21:04AM +0100, Lukas Ocilka wrote:
What should we achieve? * Less dependencies * No more cyclic issues
OK. What are the offending dependencies? Do we have a list somewhere (in autobuild?) that we can pull out to the light?
Coolo, Rudi, could you, please, send us the list of YaST-related packages that are in a cyclic build-loop? Or just any other similar problem? We have such list, right?
I'm not sure about the issues, but you could find the full list of dependencies in autobuild (attached). Michal
participants (5)
-
Duncan Mac-Vicar Prett -
Klaus Kaempf -
Lukas Ocilka -
Martin Vidner -
Michal Svec