On 2019/10/14 18:17, Ed Gray wrote: > Hi Kurt, > > I realise ports is developed on current but I am not running current > as I'm not a developer. This thread was originally about a port that > came from FreeBSD and wasn't part of current but was attached to the > list several years ago.
The port did not come from FreeBSD, I wrote it myself. Current is not just for developers, it is for anyone. We work on a single branch of development - it is not a separate branch where things are tried before going into a release. It is never intended to be unreliable (though obviously releases are cut at a time when we feel bigger changes have matured). The main thing with -current is that it's fluid and sometimes interfaces and libraries change, as a result of this you need to be prepared to do another upgrade of base+packages if it's been a while since you last updated and you want to install a new package. > Being new to this list I assumed it wasn't limited to ports in current > but I can appreciate that there are only limited developers in the > project and it may not be possible to provide advice or ports for > previous releases. > > I understand that Stuart and Antoine have committed this to current. I > was trying to test on 6.4 release and hit some problems, I will do > some more reading about the ports system and try to confirm if there's > something wrong on my machine. I gather that 6.6 is getting ready for > release and I would like to upgrade to the most recent but have not > had time to do so. Soon. While I can't say what's currently available will be the final release (sometimes last minute changes occur), if you pick up a snapshot now that identifies itself as 6.6 (before new "6.6-current" ones are available) you can cleanly upgrade from there to the 6.6 release and switch back to releases again at that point.
