Version number of openjdk6 port

[John Baldwin]

On 4/8/11 3:11 PM, Jung-uk Kim wrote:
> On Friday 08 April 2011 10:39 am, John Baldwin wrote:
>> Please consider using a better version number for the openjdk6
>> port. Right now it uses a version number of 'b20_7' which due to
>> the way package version works, is considered less than 0:
>>
>> % pkg_version -t 0 b20_7
>>
>>
>> Why does this matter?  cfengine uses 'pkg_info -E pkg_name>0' to
>> test if a package is installed.
>
> Then, I would say cfengine is broken. "0" in that version match string
> is package dependent, not major, minor, or whatever.  For example:
>
> %pkg_info -E 'avahi>0.6.20'
> avahi-0.6.29
> %pkg_info -E 'openjdk6>b0'
> openjdk6-b22_4
> %pkg_info -E 'mplayer>1.0.r0'
> mplayer-1.0.r20110329

Hmm, I can probably workaround this then using an explicit comparison
rule (so it doesn't use >0).  It would be nice if we had an official
way to match a package with "any version".  Perhaps
"pkg_info -E 'pkg-*'" if we assume that package names can never have
dashes in them (to avoid problems, with, say, 'foo-*' matching both
foo-1.0 and foo-bar-1.0.).  Oh, we already have those types of packages:

xorg-7.5            X.Org complete distribution metaport
xorg-apps-7.5_1     X.org apps meta-port

The problem is how can software generically say "is any version of the
foo package installed".  It would seem we don't support that currently?

-- 
John Baldwin