From owner-freebsd-ruby@FreeBSD.ORG Sat Nov 12 00:19:31 2011 Return-Path: Delivered-To: ruby@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECF84106568B for ; Sat, 12 Nov 2011 00:19:31 +0000 (UTC) (envelope-from astounding@gmail.com) Received: from mail-qw0-f47.google.com (mail-qw0-f47.google.com [209.85.216.47]) by mx1.freebsd.org (Postfix) with ESMTP id ABDBD8FC1F for ; Sat, 12 Nov 2011 00:19:31 +0000 (UTC) Received: by qabj40 with SMTP id j40so4750166qab.13 for ; Fri, 11 Nov 2011 16:19:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=3NGoYNItH+qhdD4uQCpdZI40xNb0mKisv2mQQm7bup8=; b=UXBM9dEB7M9RRqnY65rv9YW2Sq8OniWImah8orFJxeiHaksh0m6qYkcMEWhqWZDKGm BXf64mUkOOh/lVPDQSNX9upxGrJpcZZGRrIicRASDQ2e/BStbyJgVVk3I3J1OCSxEyj+ XpadbKpsf2yI3U9klSAwn1I4/+tHP4Zy639ps= MIME-Version: 1.0 Received: by 10.224.177.68 with SMTP id bh4mr10496610qab.48.1321055527837; Fri, 11 Nov 2011 15:52:07 -0800 (PST) Received: by 10.224.28.141 with HTTP; Fri, 11 Nov 2011 15:52:07 -0800 (PST) In-Reply-To: References: <20111111143115.5bf5d195.stas@FreeBSD.org> Date: Fri, 11 Nov 2011 16:52:07 -0700 Message-ID: From: "Aaron D. Gifford" To: ruby@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Re: What changed? (gem command missing in 1.9) X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Nov 2011 00:19:32 -0000 I'm not familiar with the inner workings of FreeBSD's port system, but is it possible that issues like 'gem' and 'rake' suddenly no longer being part of the lang/ruby19 port (due to the aforementioned outdated versions) could be dealt with during some sort of post-install hook while installing the lang/ruby19 port, a hook that could then install devel/ruby-gems and devel/rubygem-rake ports so that the executables that previously were always part of lang/ruby19 will still be automatically installed with that port? Speculating, Aaron out.