On Friday 10 February 2006 16:33, steven mestdagh wrote: > > I know that ports are associated with each release, so that I can't run > > current ports without running -CURRENT. However, I couldn't tell if the > > -STABLE ports were "frozen", or if they get updated during the six months > > that -STABLE is, well, -STABLE. > > -release ports are frozen, and may be updated if really necessary. the > branch containing those updates is called -stable.
Ah! > > I.e., if something in ports is broken, > > because of an ftp path change, does it get fixed and a new ports.tar.gz > > generated, or does it wait? > > only security issues and major reliability problems are fixed in -stable. > ftp paths are not fixed... Well, I was able to figure out how to grab the file and where to put it (so that make install would see it) pretty quick. It's not like it was a show-stopper :-) > > Do I need to be running -CURRENT to be able to > > help in this regard? > > if you want to test new ports or port updates/fixes, yes. > see also FAQ 5.1 for more info about the different branches, and FAQ 15 > for packages/ports related things. Thanks for the tip. Heading there now. > no, but it appears to be a problem in -current as well. in this case, > the port has a maintainer, so you should contact him first, but i > presume he is also reading this list :) Well, not everybody is going to read all the way to the bottom of a newbie's email, especially when the email doesn't even mention their port for three paragraphs. I'll tickle him later. Thanks for the quick response, and thanks again for the great OS! David Bishop
