From owner-freebsd-current Mon Mar 6 13:38:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 570E137BAAC for ; Mon, 6 Mar 2000 13:38:22 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id WAA12037 for freebsd-current@freebsd.org; Mon, 6 Mar 2000 22:38:21 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id WAA15722 for freebsd-current@freebsd.org; Mon, 6 Mar 2000 22:37:22 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: openssh question Date: 6 Mar 2000 22:37:22 +0100 Message-ID: <8a18ei$fb1$1@bigeye.rhein-neckar.de> References: To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG William Woods wrote: > Now that openssh is in the base system, I assume it will no longer > be in the ports. I expect the port to be maintained for the remaining lifetime of the 3.x branch. This is of no concern to 4.x users, of course. > How do we update it, ie, when a updated version comes out. OpenSSH doesn't really have releases. The upstream version is straight out of the OpenBSD repository. I assume several of our developers monitor the OpenBSD commits and will carry over any changes. > I would rather not make world just to update that. How do you handle updates to any other part of the system? Why do you consider openssh a special case? You can usually update individual parts of FreeBSD without doing a "make world". cd /usr/src/... && make -jX install && make clean. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message