[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
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.

Jeff

Schaefer, Doug wrote:
You also need a custom metadata repository. Maybe an artifact repo and touchpoints as well. But you need the metadata repo to represent the RPMs/debs as IUs to the rest of the world.
 
Doug.


From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Jeff McAffer
Sent: Wednesday, August 20, 2008 9:07 AM
To: P2 developer discussions
Subject: Re: [p2-dev] P2 UI improvements: have a look at YaST?

That is do-able by design today.  What we are missing is the relevant touchpoints.

Jeff

Schaefer, Doug wrote:
My thinking was for something like CDT where we could create a
dependency on having a gcc installed. That way, when you install CDT, p2
would also go out and install the RPM or deb, etc., that provided gcc.
You could do it the other way around, but then you'd have to do it for
each distro you supported.

D.

  
-----Original Message-----
From: p2-dev-bounces@xxxxxxxxxxx 
[mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Andrew Overholt
Sent: Tuesday, August 19, 2008 3:55 PM
To: P2 developer discussions
Subject: Re: [p2-dev] P2 UI improvements: have a look at YaST?

    
:), But YaST doesn't help me on my Ubuntu or Fedora boxen. 
      
Or is there 
    
Linux community efforts at unifying package management?
      
There are always efforts going on in that space.  Will they 
ever come to fruition?  Who know.  Most tools can now use 
each other's metadata, FWIW.

Andrew
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

    
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
  

_______________________________________________ p2-dev mailing list p2-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/p2-dev