how to update ports?

I feel like a newbie here,but google is getting worse and worse over the time in search results

in the past I use portsnap,but not anymore, so, running
git pull in
Code:
/usr/ports
returns:
Code:
fatal: not a git repository (or any parent up to mount point /usr)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

how to update /usr/ports ?

Thanks

Btw, the AI is making the humanity just dumb,google is a shi$# now
 
how to update /usr/ports ?
You can only do a git pull if it's actually a git repository. I'm assuming your current /usr/ports was previously populated by portsnap(8), this is NOT a git repository. So, delete everything in /usr/ports/ and do a git clone of the ports tree. (It has to be empty, you cannot clone over existing files).


You have to clone it first, then you can keep it updated with git pull.
 
You can only do a git pull if it's actually a git repository. I'm assuming your current /usr/ports was previously populated by portsnap(8), this is NOT a git repository. So, delete everything in /usr/ports/ and do a git clone of the ports tree. (It has to be empty, you cannot clone over existing files).


You have to clone it first, then you can keep it updated with git pull.

are the default ports from the instalation memstick,there is any diference?

and from handbook
git clone https://git.FreeBSD.org/ports.git /usr/ports

The switch
Code:
--depth 1
will install 15.1-RELEASE ports? (sorry for the newbie question)
 
If you have /usr/ports/distfiles and/or /usr/ports/packages that already holding some contents and are NOT dedicated filesystem or dataset, be sure to backup (or move) outside of /usr/ports before deleting contents of /usr/ports.

If not yet, I strongly recommend both /usr/ports/distfiles and /usr/ports/packages to be dedicated filesystem (for UFS) or datased (for ZFS).

Both are NOT parts of the ports repository itself (intentionally untracked).

I've experienced changes in repository type 2 times (first CVS to Subversion, and next Subversion to Git) and repository needed to be blanked before pulling new style of repository. And there are no assurance that repository is being Git forever (i.e., in case Git itself is abandoned and no longer supported).
 
Back
Top