|Re: [p2-dev] P2 UI improvements: have a look at YaST?|
It depends on the level of integration you are talking about. |
At the simplest level say you have some RPM X v1.2.3 that you want to have installed by p2. you need an IU (say iu_X) that has touchpoint type RPM and an action that runs rpm -i @artifact (or some such). the RPM touchpoint has an rpm action that runs the rpm command. There is no need to particularly have the rpm in the artifact repo unless you want p2 to deliver it too. Here rpm takes care of getting all the prereqs etc. p2 is just choreographing.
If you want to go the next step then you create a publisher action that interprets the dependency info in an RPM and generates IUs that have more info. Then you can use p2 to do more reasoning. This is good as you get more intereaction in p2 but bad in that p2 may not interpret things the same way as rpm so users may get misled. I don't know if you can force rpm et al to do things that they would not normally do so it is unclear if this really works.
If you want to go the next level and have the rpm database surface as a p2 repo then yes, you can follow the same model as we do with the updatesite repos and have the publisher create IUs for the various rpms in the database for interpretation by p2.
Schaefer, Doug wrote: