There are a number of ports that hardcode the OpenBSD version into
paths. Consequently, each time the OpenBSD version is incremented,
some poor guy needs to search the tree, go through the list, and
bump the package version of these ports.
Espie has suggested that we should tackle this problem at the root
and try to remove the useless version from the path names. If
anybody wants to look into this, here's a breakdown of the current
offenders:
* Ruby
Specifically, binary modules are placed under MODRUBY_ARCH which is
something like ${MACHINE_ARCH}-openbsd${OSREV}. By comparison, Perl
simply uses ${MACHINE_ARCH}-openbsd.
databases/ruby-bdb
databases/ruby-ldap
devel/ruby-ncurses
devel/subversion
lang/rubinius
lang/ruby/1.8
lang/ruby/1.9
net/rrdtool
net/ruby-pcap
net/ruby-pcaprub-msf
textproc/eruby
textproc/gonzui
textproc/ruby-hyperestraier
www/ruby-passenger
x11/kde/bindings3
* GNU part 1: GCC
GCC and related toolchain products put stuff under CONFIG, defined
as ${MACHINE_ARCH}-unknown-openbsd${OSREV}.
devel/libf2c
devel/libf2c-old
lang/g77
lang/g77-old
lang/gcc/3.3
lang/gcc/4.2
lang/gfortran
lang/llvm-gcc4
* GNU part 2: Emacs
Similar to GCC, components are stored under GCCARCH, which expands to
${MACHINE_ARCH}-unknown-openbsd${OSREV}.
editors/emacs21
editors/emacs22
editors/emacs23
editors/xemacs21/stable
* Miscellaneous others:
lang/STk
lang/swi-prolog
math/octave
x11/e17/e
--
Christian "naddy" Weisgerber na...@mips.inka.de
