From: Didier D. <did...@im...> - 2004-05-14 09:34:04
|
A additional syntax could use a LDAP filter obr install "Service Binder" (&(bundle-version>=3D1.0.0)(!(bundle-state=3D= alpha))(signature=3D*)) osc...@li... a =E9crit: >Send oscar-osgi-devel mailing list submissions to > osc...@li... > >To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/oscar-osgi-devel >or, via email, send a message with subject or body 'help' to > osc...@li... > >You can reach the person managing the list at > osc...@li... > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of oscar-osgi-devel digest..." > > >Today's Topics: > > 1. Re: Proposed OBR command syntax (Richard S. Hall) > >--__--__-- > >Message: 1 >Date: Wed, 12 May 2004 19:59:14 +0200 >From: "Richard S. Hall" <he...@un...> >To: oscar-devel <osc...@li...> >Subject: Re: [oscar-devel] Proposed OBR command syntax > >Stephane Frenot wrote: > > =20 > >>Yes, I already have such problems on my inner applications. >>All bundle managing scheme (rpm, deb, ebuilds) map version to archive >>names... obr should also do that. I think the earlier the better... >>=20 >> >> =20 >> > >There are many issues here: > > 1. OBR is just intended to be simple. > 2. OBR meta-data is exactly the bundle meta-data (modulo some additio= ns). > 3. Something that solved every problem would be great, but I don't > have the time to do it. > >Related to this, while working out at the gym, I began to start to think= =20 >about the fact that OBR meta-data is simply bundle meta-data, thus this=20 >means that we must probably allow spaces in bundle name. OBR "bundle=20 >name" is just the manifest "Bundle-Name", which is intended to be a=20 >human readable string. > >And more to the point, we have to realize that what we are debating is=20 >the command-line syntax to the bundle repository service. If you use the= =20 >new OBR panel for the GUI shell, then these issues sort of go away,=20 >because the user just clicks on the one they want. Thus, if there are=20 >(eventually) multiple versions, they can easily select the one they want= =20 >with the GUI and afterwards Bundle-UpdateLocation is automatically used=20 >to update that installed branch. > >The [proposed] meta-data for the new OBR probably covers most of the=20 >scenarios and it doesn't seem like command-line syntax should dictate=20 >design. > >So, while syntax like... > > obr install "Service Binder";1.2.0 > > or for non-space bundles: > > obr install log;1.1.0 > >...may seem a little verbose, is it really a problem? > >-> richard > >p.s. Most people do not really realize the fine level of decision making= =20 >that goes into project management, huh? :-) > > > >--__--__-- > >_______________________________________________ >oscar-osgi-devel mailing list >osc...@li... >https://lists.sourceforge.net/lists/listinfo/oscar-osgi-devel > > >End of oscar-osgi-devel Digest > > =20 > --=20 --------------------------------------------------------- Didier DONSEZ Laboratoire LSR, Institut Imag, Universite Joseph Fourier Bat. C, 220 rue de la Chimie, Domaine Universitaire BP 53, 38041 Grenoble Cedex 9, France GPS : lat 45=B011'37"N, lon 05=B046'15"E Tel : +33 4 76 63 55 49 Fax : +33 4 76 63 55 50 mailto:Did...@im... URL: http://www-adele.imag.fr/~donsez --------------------------------------------------------- |