From owner-freebsd-ports@FreeBSD.ORG  Sun Jan 30 12:51:15 2005
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3858C16A4CE; Sun, 30 Jan 2005 12:51:15 +0000 (GMT)
Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 0389643D2F; Sun, 30 Jan 2005 12:51:15 +0000 (GMT)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by cyrus.watson.org (Postfix) with SMTP id B7CB846B35;
	Sun, 30 Jan 2005 07:51:14 -0500 (EST)
Date: Sun, 30 Jan 2005 12:50:37 +0000 (GMT)
From: Robert Watson <rwatson@FreeBSD.org>
X-Sender: robert@fledge.watson.org
To: Xander Damen <xdamen@sci.kun.nl>
In-Reply-To: <41FCB39C.5010000@sci.kun.nl>
Message-ID: <Pine.NEB.3.96L.1050130124908.15336E-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: perl@freebsd.org
cc: freebsd-stable@freebsd.org
cc: freebsd-ports@freebsd.org
Subject: Re: [HEADS UP] perl symlinks in /usr/bin will be gone
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jan 2005 12:51:15 -0000

On Sun, 30 Jan 2005, Xander Damen wrote:

> Why would upgraded systems cause problems? I don't think the
> upgradesystem will delete any existing symlinks? 

I don't know about other people, but I use incremental upgrades for only
minor releases on larger multi-user systems, generally.  Because of the
level of effort and typical differences between releases, I want a "break
in" period in which I can check for incompatibilities, etc, before taking
the new system live.  This means that there is no "upgrade", there's only
a "new install" -- the user data is migrated.

Robert N M Watson


> 
> Xander
> 
> Lupe Christoph wrote:
> 
> >On Saturday, 2005-01-29 at 21:24:25 +0100, Anton Berezin wrote:
> >  
> >
> >>Unless I hear too many cries "don't do that" (with justification), ...
> >>    
> >>
> >
> >"don't do that", ever.
> >
> >Eben postponing this to the time 6.0 comes out does not change it. Any
> >upgraded system will fail in interesting and mysterious ways.
> >
> >I see no benefit in not having a /usr/bin/perl, and I see many problems
> >with it. Even when it does not affect my two insignificant ports, I'm
> >against it.
> >
> >If you are still planning on going through with this, please take the
> >idea to the perl5-porters list first. perl5-porters@perl.org
> >
> >My 2 Eurocents,
> >Lupe Christoph
> >  
> >
> 
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>