Stefano Lenzi wrote:
Alin Dreghiciu wrote:
On 9/23/07, Stefano Lenzi <[EMAIL PROTECTED]> wrote:
...
It's not the clement project which needs to be changed for you request,
but the "bundlerepository" project (Look at
RepositoryImpl.deploy(boolean):513), because the location of the bundle
is provided by the bundlerepository.
I did imagine that :)
Finally, I think that would be useful to have a way to track where the
bundle came from, but it also useful to have an URL which do not depend
from the bundle-version so that make easy the update of the bundle.
The question is: how generic the url handler should be. The one that
I was
thinking of as part of pax runner was a kind of url where you could
express
your requirements for the kind of bundle you need. As more specific
you get,
better the match. This kind of url could then be generated by
RepositoryImpl
and specify only the symbolic name in the filter and then by update time
during resolving the url it could use as a strategy to get the latest
version of the bundle. But somehow this should be also customizable
as not
always when I do want an update I want to get the newest bundle as a
version
change could brake the api.
The location related to a bundle can not be customizable because it's
related to the location used to install the bundle
Still, I do not have enough knowledge about the
whole process. But I will :) as long as I will work on the pax runner
obr
handler, that only if you/felix guys will not implement the handler
in an
OBR implementation independent way and packaged as a separate bundle.
As far as I know the OBR URL is Felix dependent because is not
specified by the RFC-0112 instead it's the location URL decide by the
Felix Team.
It's worth to notice the current OBR URL syntax maximize the update
chances because it doesn't bind the bundle to repository nor
bundle-version, but doesn't store any information about where OBR
downloaded the bundle from.
That is correct. The OBR location URL is not part of RFC-112, but was
chosen to make deployment flexible. Keep in mind that the location
cannot be changed for the entire time a bundle is installed. Thus, if
you try to encode information into this URL and then want to change it,
you are out of luck and have to uninstall it.
OBR uses a meaningless URL because it wants to make sure that it can
easily update a bundle from any version to any version without any
repercussions. Further, you are not guaranteed about the starting state
of an installed bundle anyway. Nothing stops the user from doing an
"update" outside of OBR, for example.
I think adding further information, such as where the bundle came from
would also be a mistake, since nothing prevents OBR from updating it
from a different place or allowing different OBR repos to be used
interchangeably, since symbolic name and version are supposed to be
globally unique. If you desire to only get your bundles from a
particular repo, then you should configure OBR with the correct repo,
for example.
-> richard
Ciao,
Stefano "Kismet" Lenzi
Alin
