[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re[2]: [equinox-dev] OBR2

Hmmm, that depends on your perspective ... the format is visible for
the programs that access the repo, which is pretty important.

Kind regards,

     Peter Kriens

JM> equinox-dev-bounces@xxxxxxxxxxx wrote on 09/23/2005 09:21:12 AM:

 >> Peter Kriens wrote:
 >> >It absolutely MUST be possible to generate the metadata from the
 >> >manifest.
 >> Well, it is not possible given the current state of bundle manifests to
 >> generate all repository metadata. For example, there is no way to 
 >> generate service dependencies.
 >> If someone invents a new capability/requirement pair, there will be no
 >> way to generate it either.
 >> For the standard package/module-related stuff, we can generate them from
 >> the manifest.

JM> Right.  What I was trying to get at before was that the XML
JM> metadata should really be an implementation detail.  What people
JM> supply to the repo is the manifest.  The fact that it munges it
JM> into some XML (whatever) representation internally need not be
JM> exposed.

JM> Jeff

Peter Kriens                              Mob +33633746480
9C, Avenue St. Drézéry                    Tel +33467542167
34160 Beaulieu, France                    Tel +15123514821
                                          Tel +33870447986
AOL,Yahoo, Skype pkriens                  ICQ 255570717