Date: Wed, 08 Oct 1997 04:42:52 -0700 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: asami@cs.berkeley.edu (Satoshi Asami) Cc: jkh@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-etc@FreeBSD.ORG Subject: Re: cvs commit: src/etc make.conf Message-ID: <25109.876310972@time.cdrom.com> In-Reply-To: Your message of "Wed, 08 Oct 1997 04:04:14 PDT." <199710081104.EAA10505@silvia.HIP.Berkeley.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
> * Remove trailing slash from MASTER_SITE_BACKUP example since it > * can lead to two trailing /'s, which is in turn an invalid URL (just > * bit me :-). > > Err, when did this become invalid? We've been fetching these > double-slash URLs for ages. I dunno, but when I tried to set this and then do anything with ports on my brand-new, freshly installed 3.0-971007-SNAP machine, fetch puked. Perhaps the double slashes no longer work now given Bill's latest changes to fetch(1)? I also notice that bash fell over in its installation because /usr/share/info was missing (I didn't install the info dist). Odd since bash wants nothing directly to do with /usr/share/info, so I think it's actually our auto-dir-entry-inserter thing which is falling over. Just yet another thing to test with. :-) > MASTER_SITE_XCONTRIB etc....) Also, just removing it will kill all > the ports with DIST_SUBDIR set because none of them have a trailing > slash now. Hmm. OK, I guess I should put it back the way it was then, but we still need to make fetch deal with empty // specs then. Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?25109.876310972>