From owner-freebsd-isp@FreeBSD.ORG Thu Aug 10 20:38:52 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8C1D16A4DD for ; Thu, 10 Aug 2006 20:38:52 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 4379E43D45 for ; Thu, 10 Aug 2006 20:38:51 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 24357 invoked by uid 399); 10 Aug 2006 20:38:49 -0000 Received: from localhost (HELO ?192.168.0.9?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 10 Aug 2006 20:38:49 -0000 Message-ID: <44DB9955.10102@FreeBSD.org> Date: Thu, 10 Aug 2006 13:38:45 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: freebsd-isp@freebsd.org References: <20060810132435.GB2636@rabbit> In-Reply-To: <20060810132435.GB2636@rabbit> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Ports/source dance X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Aug 2006 20:38:52 -0000 Mark Bucciarelli wrote: > No port upgrade for rubygem-rail as of yet. No commits to CVS > for the port either. :( The alert was posted only 16 hours ago, > which isn't _that_ long. But rails is back at 1.1.2, which is > already a version behind, so I expect I should upgrade > rubygem-rails from source today. > > Should I create my own port (somehow, never done that) and > install from that? Or is there an easier way? > > I guess the broader question is how to handle security upgrades > when the port isn't ready. First off, you posted to the wrong list, you should have posted this to freebsd-ports@, ideally _after_ you contact the maintainer for the port (which can be found in the port's Makefile). To answer your question more usefully, the Porter's Handbook (on the FreeBSD web site) has a lot of good information about how to create and maintain ports. If you are lucky, the following will work for you for a quick and dirty update till the maintainer (or you) have a chance to do a more thorough job of it. If you're not lucky and need help, please follow up with the maintainer, and the freebsd-ports list if needed. cp -Rp /usr/ports//rubygem-rail ~/ cd ~/rubygem-rail vi Makefile Update version information to the desired version make makesum Use some out of band method to try and determine that the files you downloaded are the right ones make If that all works, then you can deinstall the old version and 'make install' the new one. Then of course it's up to you to conduct your typical quality assurance process to make sure that the new version works for you, etc. hth, Doug -- This .signature sanitized for your protection