From owner-freebsd-www Mon Aug 24 02:04:36 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA21923 for www-outgoing; Mon, 24 Aug 1998 02:04:36 -0700 (PDT) (envelope-from owner-freebsd-www) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA21916 for ; Mon, 24 Aug 1998 02:04:34 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca10-63.ix.netcom.com [205.186.214.63]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id CAA20028; Mon, 24 Aug 1998 02:03:37 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id CAA08341; Mon, 24 Aug 1998 02:03:33 -0700 (PDT) Date: Mon, 24 Aug 1998 02:03:33 -0700 (PDT) Message-Id: <199808240903.CAA08341@silvia.hip.berkeley.edu> To: www@FreeBSD.ORG CC: Ulf Vedenbrant Subject: [uffe@swip.net: Re: ports tree unstable now] From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-www@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Date: Mon, 24 Aug 1998 10:58:32 +0200 (MET DST) From: Ulf Vedenbrant To: postmaster@FreeBSD.ORG cc: asami@FreeBSD.ORG Subject: Re: ports tree unstable now Hi! This might be the wrong way to report an eventual bug. But..;-) When browsing for example on http://www.uk.freebsd.org/ports/archivers.html You might want to ftp from ftp://ftp.uk.freebsd.org/pub/FreeBSD/FreeBSD-current/ports/archivers/arc.tar But you get ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/ports/archivers/arc.tar I.e the ".uk." is missing in the link. Is this by design? Not sure since then there will no real need for the mirrored server unless you do a direct ftp to it. Regards /Uffe On Sun, 23 Aug 1998 asami@FreeBSD.ORG wrote: > Hello ports users, > > As some of you may have noticed, the ports tree is currently > undergoing major overhaul. Some new variables have been added to > bsd.port.mk, and some existing ones have disappeared. Also, the > recent perl5 upgrade has caused a few dozen ports to simply stop > working. I apologize for the confusion. > > We are fixing them now, but it will take a few more days. In the > meantime, I suggest that you be extremely careful if you are cvsupping > the ports tree. Some things are really broken and will cause others > to fail utterly. > > At least, make sure you have the latest bsd.port.mk if you still want > to venture into dangerous waters. If you use an old bsd.port.mk with > the latest ports you may see an entire port install files in a wrong > location (/usr/local vs. /usr/X11R6). (I've heard someone installed > ports/x11/XFree86 with and old bsd.port.mk and have the whole X > installation end up in /usr/local -- that's disaster, to say the > least! ;) The latest version of this file (the Id string) is 1.284 > for -current and 1.227.2.46. > > I will post another announcement to this list when I believe all ports > are fixed. Until then, I recommend people who aren't following the > ports list or cvs list to use packages. Packages-stable is being > populated now as I speak, those should give you much better luck than > ports. > > Again, sorry for the inconvenience. > > Satoshi (and the great ports team) > > This is the moderated mailing list freebsd-announce. > The list contains announcements of new FreeBSD capabilities, > important events and project milestones. > See also the FreeBSD Web pages at http://www.freebsd.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-announce" in the body of the message >