Usually this time of year, we need to remind people that ports-current
follows source-current.

There is absolutely no simple way to compile port-current with an older
source, and be succesful.

Again, this time, there are specific reasons for that.

- Dale Rahn and Kurt Miller are completely revamping our ld.so to be
compliant to the actual specs. This is a *huge* change, and it won't
be backported to 3.6/3.7/3.8, because it invades a lot of areas.
So far it has fixed at least two big pieces of software (karbon in kde and
evolution in gnome), and it's likely more things have become way more stable.
- there are huge modifications happening in the package tools. Some checks
have become more stringent, and people submitting ports built on an older
system will often not see them.
- m4 has become more susv3 compliant, and simpler to use as a replacement
to gnu-m4. Accordingly, some autoconf scripts may work like a charm, where
before you would have needed some patches. Weird errors will ensue if you
don't have the right m4.
- there are new keywords in pkg_add.

There are also all kinds of changes that will happen, including the 
continuation of i18n support, and (slowly) more C99 support.

People following current won't notice: there will be less stuff to patch
in software we port, and so we won't patch it. People following stable will
see all kinds of weird reports if they try to build current ports.

There is nothing wrong with staying with OpenBSD 3.7 or 3.8, but if you
do, stick to the stable branch of the ports tree...

Reply via email to