Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [p2-dev] Show IU source repository

Ciao @ll :)
I think this discussion is worth expanding, so I'm throwing in my 2
cents ;)

It's true that p2 only cares about fulfilling the change request no
matter the resources (repos) needed for that and as such does not link
the repositories it installed from (or the categories, but that's
another issue I'm having) to the installed content. However, to the user
it's pretty important to know where things came from, for a few reasons:
1.) (s)he might want to reproduce the exact same installation, with the
same repositories
2.) (s)he just wants to know where things came from
3.) (s)he wants to see if the installation time was OK, and this highly
depends on where things came from

So, I'm also thinking that p2 should record the repositories things came
from in the profile, that way reproducing an install only needs the
profile. The information should be there anyway, we do have a cache of
repositories lying around, all that needs adding is a way to associate a
provchange with a set of repos, but maybe I'm looking at this from the
wrong angle..

Thanks! :)

-----Original Message-----
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On
Behalf Of Henrik Lindberg
Sent: Saturday, June 26, 2010 4:59 AM
To: P2 developer discussions
Subject: Re: [p2-dev] Show IU source repository

User installs from one repo, then uninstalls, then installs from other
repo. You don't know, nor should you care from which repo a bundle was
installed (p2 picks a bundle from what it already has, and uninstalled
things may still be around). If there is a difference between 'test'  
and the 'release' you have to reflect that at the bundle or feature
level (different version).

Using catagories may work

- henrik

25 jun 2010 kl. 09.04 skrev Michael Mangeng

> hi!
> thanks for the response.
> the main purpose is for our customers. we want them to see wether they

> installed a plugin from our stable repo or from our testing repo.
> (we're a building automation company which provide drivers for various

> bus systems. if a customers installs something from the testing 
> repository we want them to be aware as long as the plugin is installed

> and not only when he clicks on "install".
> if there is no other idea i'm thinking about simply checking the 
> configured repos for the already installed plugins - then print the 
> name of the repo where the plugin is available :-)
> greetings,
> michael
> Am 24.06.2010 um 15:04 schrieb Henrik Lindberg:
>> This can become quite complicated as the same meta data and the same 
>> artifacts can be found in multiple repositories, so when installing 
>> X, the resulting change of the installation can consist of downloads 
>> from different repositories (and from different mirrors), or even 
>> from other locations on the users file system (another eclipse 
>> installation).
>> Why does it matter where the bits came from? They are supposed to be 
>> identical if they have the same name and version. If they do not, 
>> then that is a quite serious problem.
>> Henrik Lindberg
>> henrik.lindberg@xxxxxxxxxxxxxx
>> On Jun 23, 2010, at 12:14 PM, Michael Mangeng wrote:
>>> hi all!
>>> got a little question where i don't know how to start:
>>> i'm showing the user a list of already installed IUs in a web-ui.  
>>> now i want to show from which repo the IU has been installed.
>>> background: we want that the user knows whether the IU has been 
>>> installed from a "stable" repo or a "testing" repo.
>>> does anyone know about an easy approach? could i handle this with a 
>>> touchpoint for the install-phase? can i store the repo location 
>>> somehow e.g. in the profile?
>>> greetings,
>>> michael
>>> _______________________________________________
>>> p2-dev mailing list
>>> p2-dev@xxxxxxxxxxx
>> _______________________________________________
>> p2-dev mailing list
>> p2-dev@xxxxxxxxxxx
> _______________________________________________
> p2-dev mailing list
> p2-dev@xxxxxxxxxxx
p2-dev mailing list

Back to the top