Hi Marc, Thanks for your reply. I think maybe this belongs to ports more than misc. But it's a general query about releases and ports as well.
My question was actually about updating the ports tree from an older release version before trying to use it rather than whether to use ports or packages. I installed 6.2 release I believe and later upgraded to 6.6 release. I pulled the release version of ports at some point and later tried to build a port which failed due to an outdated dependency. My version of the ports tree was outdated but even the newer 6.6 stable version was also outdated. When I sent my original email 6.6 was still one of the supported releases along with 6.7. I guess my question is if I run 6.x release and want to build port xyz can I expect a port to build using the ports tree that came with the 6.x release or must I always use at least the stable version of the ports tree? The following question is then if I have a problem building a port due to an outdated dependency on a supported release should I report it as an issue with the port even if a newer release of openbsd does not have the issue? Regards Ed Gray On Wed, 28 Oct 2020, 7:07 am Marc Espie, <es...@nerim.net> wrote: > On Sun, Oct 11, 2020 at 09:12:13PM +0200, Ingo Schwarze wrote: > > Hi Ed, > > > > Ed Gray wrote on Sun, Oct 11, 2020 at 07:21:32PM +0100: > > > > > I'm still fairly new to openbsd and the idea of using ports > > > in general rather than binary packages. > > > > You are usually better off using packages than using ports, > > especially as a new user. > > > > Even as an experienced user doing lots of development and minor > > amounts of ports development, i use packages most of the time. > > As one of the persons *responsible* for keeping the ports system > working, I do use packages all the time. > > Ports are on my development setup. > > The machine I write this mail from uses packages, > with about 3 ports that are just there because not committed yet. >
