Solved What's the new alternative to portsnap

[balanga]

I just did a search on this topic and found Thread 76463/, but didn't feel like combing through 120 msgs...

AFAIUI git the big new thing, so how do I go about populating /usr/ports/

https://www.freebsd.org/ports/installing/ only mentions portsnap() and svn() so I'm not sure if git is the way to go.

 

[rawthey]

Install net/gitup then run gitup ports

 

[balanga]

I get 'invalid argument'

 

[Alain De Vos]

I do the following,

rm -r /usr/ports/* /usr/ports/.??*
cd /usr/ports/
git clone --branch 2021Q2 https://git.FreeBSD.org/ports.git /usr/ports

And to update,

cd /usr/ports
git pull --rebase

 

[scottro]

Not sure how much of the default gitup file has been fixed. Your /usr/local/etc/gitup.conf should have a ports section that reads

         "repository_path"  : "/ports.git",
                "branch"           : "main",
                "target_directory" : "/usr/ports",

There is more in there, but the repository path line was wrong fro awhile, also the branch line might say master--if it does, change it to main.

 

[balanga]

There is more in there, but the repository path line was wrong fro awhile, also the branch line might say master--if it does, change it to main.

Thanks. That's what was missing.

 

[drhowarddrfine]

As always, the instructions in the Handbook worked fine for me for using git

 

[zirias@]

Just for completeness:

portsnap is planned to be removed at some point in time. But it's still part of 13.0-RELEASE, so it won't go away until (earliest) EOL of the 13-STABLE branch. As far as I know, there is no "replacement" planned so far.

Apart from that, it was always an alternative to get the ports tree directly from its source repository, which worked using svn until recently, but is now switched to git. Using the repository directly always had some advantages, one of them being that you can select the branch you want (while portsnap was always based on the "main" branch, "latest" in pkg repos).

For people wanting to just fetch from repos and not interested in doing development themselves, there was svnup in the past, and there's gitup now to replace it. Those are tools that just fetch (and don't support anything else) and aim for ease of use (one simple command…)

As for the config issue with the branch name: the "master" branch was renamed to "main" quite some time ago, and the default config of gitup followed that. If you still have a config referring to "master", it seems you didn't upgrade ports/packages for some time

 

[richardtoohey2]

I think the quaterly pkg install of gitup has the wrong configuration.

There was a blip when portsnap wasn't working (during the migration to git) but now both tools do the job - just need to watch out for the config issue in gitup.

I think gitup might use a lot of memory so if you are on a 512M VM or similar you might want to stick to portsnap (think there's been a fix for the memory usage).

 

[bsduck]

I think the quaterly pkg install of gitup has the wrong configuration.

I confirm.