Cvsup refuse confusion
Charles Howse
chowse at charter.net
Mon Sep 22 10:51:34 PDT 2003
> On Monday 22 September 2003 10:07 am, Charles Howse wrote:
> > > On Monday 22 September 2003 09:39 am, Andrew L. Gould wrote:
> > > > On Monday 22 September 2003 11:13 am, Charles Howse wrote:
> > > > > Hi,
> > > > > I'm trying to eliminate all the non-English ports and
> > > > > documentation. I've deleted the relevant directories in
> > > > > /usr/ports and /usr/share/doc, But they reappear on subsequent
> > > > > cvsups. Where have I gone wrong?
> > > > >
> > > > > ********* /etc/cvsupfile *********
> > > > >
> > > > > *default host=cvsup11.FreeBSD.org
> > > > > *default base=/usr
> > > > > *default prefix=/usr
> > > > > *default release=cvs
> > > > > *default tag=RELENG_4_8
> > > > > *default delete use-rel-suffix
> <snip>
> > > > >
> > > > >
> > > > > Thanks,
> > > > > Charles
> > > >
> > > > Check for the existence of the folder /usr/sup. If it exists,
> > > > move your refuse file to it.
> > > >
> > > > Also, should you be refusing to update ports/INDEX? I refuse the
> > > > non-English ports; but my refuse file does not include
> > > > ports/INDEX.
> > >
> > > Yes, because you are supposed to rebuild INDEX after
> every cvsup of
> > > ports-all. If you pick and choose the port collection, you will
> > > probably break "make index" and then the upate tools won't
> > > work as you
> > > would expect. Since you are going to rebuild INDEX or
> INDEX-5 after
> > > each cvsup, refusing it prevents cvsup from redownloading it.
> > > It takes
> > > several minutes to download even across a 100Mbps networkd.
> > >
> > > If you use portupgrade, you also have to run "portsdb -u"
> after you
> > > create and updated INDEX.
> >
> > OK, the OP is getting confused. ;-)
> > I have moved my refuse file to /usr/sup/refuse
> > I have deleted the directories in /usr/ports and /usr/share/doc that
> > I don't want.
> > I will cvsup when we get this straightened out in my mind.
> >
> > Dr. Seaman says run 'make index' *OR* portsdb -Uu after cvsup.
> > Kent says run 'portsdb -u' *AFTER* make index.
> >
> > What is our consensus?
>
> You don't do a "make index" and a "portsdb -uU". You only need to run
> "portsdb -u" after a make index.
>
> They do the same thing; however, Kris has a script that
> writes a bitch
> message to -ports when "make index" fails. There isn't anything
> comparable for portsdb -U. In addition, portsdb -U has always
> produced
> a large number of error messages that I don't see with "make index".
>
> I have also found that you typically get a slightly larger
> port count on
> the "portsdb -u" when you run "make index".
>
> FWIW, I run portsdb -U when "make index" fails. I think they are both
> tools that meet slightly different needs. I think "portsdb
> -U" handles
> an incomplete /usr/ports and "make index" doesn't.
OK, I'm starting to get the drift here.
Thanks.
More information about the freebsd-questions
mailing list