Hey guys:

During the teleconference call today, we briefly discussed this.  Here's the 
summary:

The Version field, as displayed on the OSCAR Package Selector (selector) is the 
OSCAR *Package* version.  In other words, to use the Ganglia package as an 
example, currently it is at 2.5.6-2.  2.5.6 is the version # of the actual 
project, 2 is the version of the OSCAR Package for Ganglia.

So how can I tell what version of the RPMs are in the actual package?

Use the <provides> tag in config.xml:

<provides>
  <type>rpm</type>
  <name>ganglia-monitor-core-gmetad-2.5.6-1</name>
</provides>
<provides>
  <type>rpm</type>
  <name>ganglia-oscar-monitor-core-gmond-2.5.6-1</name>
</provides>
<provides>
  <type>rpm</type>
  <name>ganglia-webfrontend-2.5.5-1</name>
</provides>

We will need to go through the config.xml to fix all the current packages, but 
I think an audit was going to take place anyway.

Final thoughts?

Thanks,

Bernard

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of 
> Jeff Squyres
> Sent: Tuesday, February 15, 2005 3:57
> To: [email protected]
> Subject: Re: [Oscar-devel] OSCAR Package versions
> 
> I think that an easy solution would be to have a second, 
> complete version number that is affiliated with the 
> underlying package version.  
> Its use is for printing/information only -- it's never used 
> in OSCAR version number comparisons -- and is therefore optional.
> 
> So for your Ganglia scenario, your package number should be 
> 2.5.6-1, and the underlying ganglia version can be set to 
> 2.5.6-1.  If you update the Ganglia opkg, then you can update 
> the upper level number (i.e., the official opkg version 
> number) to 2.5.6-2 while leaving the lower level number 
> (ganglia RPM, so to speak, although that's not 100%
> accurate) as 2.5.6-1.
> 
> So opd (and various other OSCAR tools) can display it something like:
> 
> Ganglia version 2.5.6-1, OSCAR packaging version 2.5.6-2.
> 
> Or, if you're in an opkg that doesn't have an underlying 
> version number, it would be displayed thus:
> 
> Ganglia, OSCAR packaging version 2.5.6-2.
> 
> Howzat?
> 
> On Feb 14, 2005, at 10:33 PM, Bernard Li wrote:
> 
> > I had an IM session with John about this earlier, but I thought I'd 
> > throw this out to the public.
> > �
> > Basically I'm trying to figure out a versioning scheme for OSCAR 
> > Packages.
> > �
> > As far as naming is conerned, there are 2 types of packages - a 
> > package which includes�RPMs or a package which configures 
> RPMs (or deb 
> > or whatever...)
> > �
> > For the first case, an example would be Ganglia.� The 
> Ganglia version 
> > is 2.5.6-1 - this is fine and dandy, so the package version 
> is 2.5.6-1 
> > too.� However, what happens when I make changes to the Ganglia 
> > _package_ (and keep the RPMs the same)?� I can't really up 
> the release 
> > number ("1") and the epoch # isn't currently displayed in the 
> > selector/OPD...� is this even the 'correct' way of using the epoch 
> > number?
> > �
> > For the second scenario, let's say I'm modifying the package 
> > ntpconfig.� It does not provide any RPMs so I can't version 
> it based 
> > on included RPMs - should I just up the version number 
> arbitrarily (as 
> > the package author/maintainer)?
> > �
> > Thoughts?
> > �
> > Thanks,
> > �
> > Bernard
> >
> 
> --
> {+} Jeff Squyres
> {+} [EMAIL PROTECTED]
> {+} http://www.lam-mpi.org/
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from 
> real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_ide95&alloc_id396&op=ick
> _______________________________________________
> Oscar-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oscar-devel
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel

Reply via email to