Portupgrade problem

Erik Trulsson erikt at update.uu.se
Fri Apr 9 12:42:07 PDT 2004

On Fri, Apr 09, 2004 at 09:34:09PM +0200, Andreas Davour wrote:
> On Fri, 9 Apr 2004, Martin Hudec wrote:
> > Hi Andreas,
> >
> > 	don't you really have atk in /usr/ports/accessibility/atk directory?
> No.
> > Perhaps look into ports-supfile.. do you have there ports-all enabled?
> No, I have it commented out, since I left all the individual ports
> collections in there instead, except for arabic, hebrew and some other
> exotic languages.

That was a bad idea, since new collections are added from time to time.
If you really feel the need to avoid fetching some ports-categories it
is better to use a refuse file instead.
Personally I stopped doing even that some time ago, since some make
targets require a complete ports tree.
Unless you are seriously short on diskspace I would strongly recommend
using 'ports-all' to a complete ports tree.

> Could it be I have made such a basic mistake as to not cvsup'ed a vital
> dependedcy?! I kind of figured the newly cvsup'ed port of cvsup would have
> included a new example file of ports-supfile if that had been the problem.

It does seem as if your ports-supfile is at fault, yes.

> One should never *expect* a computer to do something I guess.
> Would something strange happen now if I added a line for
> 'ports-accessability' in my ports-supfile and tried to cvsup again?

Probably not.

> I guess I *really* should do a pkgdb -Uu then?

<Insert your favourite quote here.>
Erik Trulsson
ertr1013 at student.uu.se

More information about the freebsd-questions mailing list