[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] OBR2
- From: Peter Kriens <Peter.Kriens@xxxxxxxx>
- Date: Fri, 23 Sep 2005 18:11:30 +0200
- Delivered-to: firstname.lastname@example.org
- Organization: aQute
Hmmm, that depends on your perspective ... the format is visible for
the programs that access the repo, which is pretty important.
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
>> 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
Peter Kriens Mob +33633746480
9C, Avenue St. Drézéry Tel +33467542167
34160 Beaulieu, France Tel +15123514821
AOL,Yahoo, Skype pkriens ICQ 255570717