Version number of openjdk6 port
jkim at FreeBSD.org
Fri Apr 8 20:28:37 UTC 2011
On Friday 08 April 2011 03:48 pm, John Baldwin wrote:
> 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
> 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
The key here is package origin, not the package name itself.
%pkg_info -qO java/openjdk6
%pkg_info -qO x11/xorg-apps
It is always safe to find its origin because there may be prefixes and
%pkg_info -qoX ko-openoffice.org
I think this would be the worse case in the ports tree:
%pkg_info -qo apr-ipv6-devrandom-gdbm-db42-184.108.40.206.3.10
More information about the freebsd-java