Date: Fri, 11 May 2001 18:37:50 -0400 From: "Otter" <otterr@telocity.com> To: "'David W. Chapman Jr.'" <dwcjr@inethouston.net>, "'Roelof Osinga'" <roelof@eboa.com>, "'Rasputin'" <rara.rasputin@virgin.net> Cc: <stable@freebsd.org> Subject: RE: What gives? Message-ID: <001101c0da6b$02f9b910$1400a8c0@zoso> In-Reply-To: <061901c0da66$8da39040$931576d8@inethouston.net>
next in thread | previous in thread | raw e-mail | index | archive | help
If you really question your ports tree, just rm -rf /usr/ports/* and cvsup again. -Otter > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of David W. Chapman > Jr. > Sent: Friday, May 11, 2001 6:06 PM > To: Roelof Osinga; Rasputin > Cc: stable@freebsd.org > Subject: Re: What gives? > > > 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" <roelof@eboa.com> > To: "Rasputin" <rara.rasputin@virgin.net> > Cc: <stable@freebsd.org> > 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:info@eBOA.com?subject=Information_request fax. > +31-58-2160293 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001101c0da6b$02f9b910$1400a8c0>