On 2018/08/02 10:16, Rudolf Sykora wrote: > > Use cvs. > > Ok. I just tried to follow the table at > https://www.openbsd.org/faq/ports/ports.html > under > Fetching the ports tree > where I understood the table in the sense to download the tar. > (At that point I haven't realized that there seems to exist just > one snapshot [not a series of them in time], so I wanted to have the ports > tree just right for the snapshot. If we only consider the newest > snapshot, I understand that using cvs and its -current branch is > just nearly the same.)
I think it's fairly pointless to have a ports.tar.gz for -current. People following current and using it for ports development are expected to keep up with cvs anyway. People not using it for ports development mostly don't need a ports tree and are better served with snapshot packages instead. (The main exception to this is if you need to use things from ports where we aren't allowed to distribute packages so you need to build them yourself.) There's no ports.tar.gz which can be guaranteed to be "just right" for any given snapshot. They are produced separately. > > No need to remove the existing files. > > No need to remove if you use cvs. Right? > But if tar is used, then the removal is needed, no? > Without it some old (say removed, no longer valid ports) > would remain. ports.tar.gz is just a tarred-up CVS checkout. You can update it with CVS using the usual flags (-Pd), this will remove old directories and add new ones as needed. If you're downloading the whole ports.tar.gz tree again to unpack then yes you will need to remove old files first, but I wouldn't recommend that.