The most common thing I find is leftovers, like a Makefile.inc or a work
directory, do a make clean on them, I periodically do a make clean in
/usr/ports. I know there is probably a more efficient way to do it, but I
just let it go for a while. You could also do it before you install
somethings, just do a make clean install, because it also cleans the
dependencies.
----- Original Message -----
From: "Roelof Osinga" <[EMAIL PROTECTED]>
To: "Rasputin" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, May 11, 2001 4:15 PM
Subject: Re: What gives?
> Rasputin wrote:
> >
> > >...
> > > -rw-r--r-- 1 root wheel 1955761 May 10 00:30 gnome
> > > -rw-r--r-- 1 root wheel 636835 May 10 02:46 kde2
> >
> > Freaky - those two both work for me.
>
> >
> > Sounds like your ports tree is shafted, because the ports work for
others.
>
> Interesting suggestion. Never mind the obvious 'how could it have
> been shafted?', but rather point out how one can verify the state
> of ones port collection. Please :).
>
> Each tarball has an unique MD5 hash. Each port release has the distinfo
> file with the MD5's it has been based upon. Hence each port can verify
> if the tarball fetched is the right one. Alternatively it can check
> if needed needed stuff like libs or execs are present.
>
> Yet how can a sysop check the correctness of the collection itself?
> As well as supporting utilities, of course. Just wipe /usr/ports and
> refetch the whole shebang? Coupled with a CVSup of the source, is it
> advisable to also wipe the /usr/src tree? Or are there diagnostic tools?
>
> Would be nice since that would be a nice first step in the diagnostic
> process.
>
> Roelof
>
> --
> _______________________________________________________________________
> eBOAź est. 1982
> http://eBOA.com/ tel. +31-58-2123014
> mailto:[EMAIL PROTECTED]?subject=Information_request fax. +31-58-2160293
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
