From owner-freebsd-ruby@FreeBSD.ORG Tue Jan 12 07:47:29 2010 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 B5B67106566B for ; Tue, 12 Jan 2010 07:47:29 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from mx0.deglitch.com (backbone.deglitch.com [IPv6:2001:16d8:fffb:4::abba]) by mx1.freebsd.org (Postfix) with ESMTP id 5E70C8FC14 for ; Tue, 12 Jan 2010 07:47:29 +0000 (UTC) Received: from sputnik.SpringDaemons.com (c-71-198-20-159.hsd1.ca.comcast.net [71.198.20.159]) by mx0.deglitch.com (Postfix) with ESMTPA id 4A63F8FC4E; Tue, 12 Jan 2010 10:47:26 +0300 (MSK) Received: from sputnik.SpringDaemons.com (localhost [127.0.0.1]) by sputnik.SpringDaemons.com (Postfix) with SMTP id 01E8CB86F; Mon, 11 Jan 2010 23:52:10 -0800 (PST) Date: Mon, 11 Jan 2010 23:52:10 -0800 From: Stanislav Sedov To: "Philip M. Gollucci" Message-Id: <20100111235210.434e6e86.stas@FreeBSD.org> In-Reply-To: <4B4C240E.4060205@ridecharge.com> References: <4B4C240E.4060205@ridecharge.com> Organization: The FreeBSD Project X-XMPP: ssedov@jabber.ru X-Voice: +7 916 849 20 23 X-PGP-Fingerprin: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581 X-Mailer: carrier-pigeon Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: ruby@FreeBSD.org Subject: Re: RF vs GITHUB and ports trouble 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: Tue, 12 Jan 2010 07:47:29 -0000 On Tue, 12 Jan 2010 07:26:06 +0000 "Philip M. Gollucci" mentioned: > Hi, > > So about 60-80% of the projects on github, *sigh*, never make releases > which means you can't download anything other then git head, or a > branch. If you are lucky a tag. > You can hardly do something with this. If the upstream projects doesn't make releases, you as a maintainer need to figure out what are the right branch points are (when the project is most stable), make snapshot of the tree and upload it somewhere, where the port can find it. > As gems move from RF to GITHUB, we're going to have lots of problems. > I.E www/rails which I can't update to 2.3.5 until this is resolved. > This certainly doesn't work with USE_RUBYGEMS and it doesn't even work > without it. Additionally, it doesn't work with the gem command (gem18 > in this case). Can you be more specific? Why the gem command doesn't work? Has something changed in gems themselves? > > As maintainer of 36 rubygems I'm definitely worried about the future and > am willing to invest some time in bsd.ruby.mk to do something, but I > have no idea what that something might be. > > Finally MASTER_SITES_GITHUB and GITHUB macro will need to go into > bsd.sites.mk. > What this HITHUB macros do? I can't find any references in the ports tree? -- Stanislav Sedov ST4096-RIPE