Re: [equinox-dev] Thoughts on write api for repository : Please add your

[Jeff McAffer <Jeff_McAffer@xxxxxxxxxx>]

Think "objects and garbage collection".
IUs are just objects that describe things you can install.  Repositories
are just memory spaces that can hold IU objects.  One can copy these
IUs from repo to repo and basically everything we use to hold IUs is a
repo.  We generally talk about "mirroring" as the verb when
taking something from one repo and copying to another.  Deleting an
IU from a repo may be done explicitly oryou can leave them there and at
some point garbage collect them.

Two additional points are critical:
- IUs are *metadata*.  They describe
things.  The are NOT the things.  So an IU for a bundle is NOT
the bundle.  The bundle is an "artifact".  Having an
IU in a repo does not imply that you have the associated artifacts in/near/beside/...
that repo

- Profiles track "installation
operations".  That is, putting something in a repo is just a
mirroring or copying operation.  It is analogous to copying files
from one drive to another.  When an IU is "installed" however,
it is added to a profile.  That profile can then be run.  Later
the IU can be uninstalled or updated in that profile.  The exact same
IU can be installed simultaneously in many profiles.  Think of profiles
as simply lists of IUs.  For fun, under the covers we may use a metadata
repo to manage this list but that is just an implementation detail.

HTH

Jeff

"Prashant Deva" <prashant.deva@xxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

06/25/2007 09:19 PM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

To	"Equinox development mailing list" <equinox-dev@xxxxxxxxxxx>
cc	Pascal Rapicault/Ottawa/IBM@IBMCA
Subject	[equinox-dev] Thoughts on write api for repository : Please add        your thoughts

Hi,
 Me and pascal were having a discussion regarding the write api for the
repositories.
I would appreciate if you all would post your thoughts on this too.
I am attaching our conversation below.

Prashant

On 6/25/07, Prashant Deva <prashant.deva@xxxxxxxxx>
wrote:
Hi,

- during the installation itself because the agent keeps
track of the 
installable unit that have been installed into a metadata repository.

ummm maybe i dont get this correctly. isnt an install a read only operation?
eg - when i am installing eclipse why 
would i want to write anything to a repository? 
 

* Nothing happen to mirrors and nothing has to happen
to mirror since you 
can not change an IU once it has been published.

Ok, let me get this. Say i have junit 3 in a repository as an IU.
When somebody wants to write junit 4 to a repository, we leave junit 3
there? Or do we delete it? 
i guess deleting or updating the jar would modify the IU for junit so we
just gotta add v4.
but then does that mean we cannot delete anything from a repository once
it has been published?

Prashant





On 6/25/07, Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>
wrote:
* Metadata repositories would be written into:
- at export / publication time, someone creates new plug-ins and makes
them
available on a repository. The other place we are using this is when we
are
generating metadata. 
- during the installation itself because the agent keeps track of the
installable unit that have been installed into a metadata repository.

* There is a need for authentication, but I think we can leave that issue
out for now because I think we have to have a global approach of the pb
for
the agent.

* Nothing happen to mirrors and nothing has to happen to mirror since you
can not change an IU once it has been published. 





             "Prashant Deva"
             <prashant.deva@gm
             ail.com>
                     
                     
      To
                    
                  Pascal Rapicault/Ottawa/IBM@IBMCA
             06/25/2007 02:06    
                     
                cc
             PM        
               "Andrew Overholt"
                    
                  < overholt@xxxxxxxxxx>



hi guys,
so i have taken a detailed look at the code. i now have a much better idea
of whats going on ;)

So i was thinking on working on providing the write support for the 
metadata api.

For this, I would like to ask you  guys some questions of course.

- Under what situations do you imagine would someone be writing to the
repositry?
- does there need to be some sort of authentication to be able to write?
- what happens to the repsository mirrors when someone writes to one
repository? do we show them as out of date.

Also any other thoughts/ideas you have regarding this are welcome.

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