Updating /usr/ports

[LuMiWa]

On Thu, 27 May 2021 17:01:52 -0700
Kevin Oberman <rkoberman at gmail.com> wrote:

> On Tue, May 25, 2021 at 9:13 PM Janos Dohanics <web at 3dresearch.com>
> wrote:
> 
> > On Mon, 24 May 2021 12:35:00 -0700
> > Kevin Oberman <rkoberman at gmail.com> wrote:
> >
> > > On Mon, May 24, 2021 at 9:41 AM Janos Dohanics
> > > <web at 3dresearch.com> wrote:
> > >
> > > > Hello,
> > > >
> > > > The Handbook says "As needed, update /usr/ports after the
> > > > initial Git checkout:
> > > >
> > > > # git -C /usr/ports pull"
> > > >
> > > > [root at frigg ~]# portversion -v | grep -c "<"
> > > > [Reading data from pkg(8) ... - 294 packages found - done]
> > > > 7
> > > >
> > > > [root at frigg ~]# git -C /usr/ports pull
> > > > [...]
> > > > 855 files changed, 8990 insertions(+), 7435 deletions(-)
> > > >
> > > > [root at frigg ~]# portversion -v | grep -c "<"
> > > > [Reading data from pkg(8) ... - 294 packages found - done]
> > > > 7
> > > >
> > > > However, you also need to 'make index' which the Handbook does
> > > > not mention:
> > > >
> > > > [root at frigg /usr/ports]# make index
> > > >
> > > > [root at frigg /usr/ports]# portversion -v | grep -c "<"
> > > > [Reading data from pkg(8) ... - 294 packages found - done]
> > > > [Updating the portsdb <format:bdb_btree> in /usr/ports ... -
> > > > 31205 port entries found
> > > > .........
> > > >
> > 1000.........2000.........3000.........4000.........5000.........6000.........7000.........8000.........9000.........10000.........11000.........12000.........13000.........14000.........15000.........16000.........17000.........18000.........19000.........20000.........21000.........22000.........23000.........24000.........25000.........26000.........27000.........28000.........29000.........30000.........31000..
> > .....
> > > > done] 12
> > > >
> > > > --
> > > > Janos Dohanics
> > > >
> > > If you don't mind being a couple of hours out of date, "make
> > > -C /usr/ports feetchindex.". The index file is generated every 3
> > > hours (I think), and it's a lot faster than making it yourself.
> >
> > Thanks, I know about 'make fetchindex' - this happens to be a
> > reasonably fast machine.
> >
> > My point is though that 'git -C /usr/ports pull' apparently doesn't
> > update the port index, and the Handbook doesn't say you need to do
> > 'make index' or 'make fetchindex'.
> >
> > Also, 'portsnap fetch' && 'portsnap update' did update the index. My
> > reading of the Handbook was that 'git -C /usr/ports pull' alone gave
> > the same result as 'portsnap fetch' && 'portsnap update'.
> >
> > > Also, the grep is not needed. 'pkg version -vl<" (or, "-vL=" to
> > > catch orphaned ports) will do the same thing. Don't worry if you
> > > are not using ports. pkg does exactly the same things for both
> > > ports and packages except for actually building ports. I thought
> > > that portversion was long gone. It's not on either v12 or 13 on
> > > my systems.
> >
> > My bad habit, thank you for the reminder!
> >
> > --
> > Janos Dohanics
> >
> If you are trying to replace portsnap, I think the answer is
> net/gitup. This only requires a single command,  "gitup ports", and
> you get your index updated along with updating all ports. I believe
> that the plan is to put gitup into the base system fairly soon. I
> have not looked at whether 14-current has gitup, yet.
> 
> And, yes, it looks like the handbook needs some work as gitup is not
> yet even mentioned. Like portsnap, gitup is for people who want to
> maintain an up to date ports tree, but not good for developers. They
> do need to use git and either generate the index or fetch it.
> --

I am using "gitup ports" and it works without problem.



-- 

“Thinking is difficult, that’s why most people judge.”

Carl Jung