From owner-freebsd-ruby@FreeBSD.ORG Mon May 4 10:25:13 2015 Return-Path: Delivered-To: ruby@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 139D4A63; Mon, 4 May 2015 10:25:13 +0000 (UTC) Received: from toco-domains.de (mail.toco-domains.de [176.9.39.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CA6701B19; Mon, 4 May 2015 10:25:11 +0000 (UTC) Received: from [0.0.0.0] (mail.toco-domains.de [176.9.39.170]) by toco-domains.de (Postfix) with ESMTPA id A8EC31B2200A; Mon, 4 May 2015 12:25:02 +0200 (CEST) Message-ID: <554748FC.1070608@toco-domains.de> Date: Mon, 04 May 2015 12:25:00 +0200 From: =?windows-1252?Q?Torsten_Z=FChlsdorff?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Johannes Meixner , ruby@freebsd.org, ports@michael-fausten.de Subject: Re: Gitlab-Port: rubygems status References: <5538AD8F.5060807@toco-domains.de> <20150423172339.GA76294@mx12.chaot.net> <553A6452.30507@toco-domains.de> <20150504095837.GA55069@mx12.chaot.net> In-Reply-To: <20150504095837.GA55069@mx12.chaot.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 May 2015 10:25:13 -0000 Hi everyone, >> a college of me - Michael - volunteered for help. :) Therefore i've >> added him to CC. > > Even better. CC to ruby@ because that's what we have mailing lists for! Done. :) >> I've created an chart of all ruby-gem dependencies excluding the groups >> "development" and "test": >> http://ports.toco-domains.de/gitlab-gem-dependencies.html >> >> There are 96 dependencies in total. >> >> - 16 are not in the ports >> - 9 are in the ports, but outdated >> - 13 are in the ports, but more actual than allowed >> - 58 are in the port and newer than needed -they should (!) be fine >> >> Until Monday i have no time to work on this stack of gems. I've already >> created a patch for devel/rubygem-gitlab_git and its dependency >> devel/rubygem-rugged. The bug-entries are linked in the list. >> >> If somebody of you decides to work on an entry, please write me an email >> and i will register it (at Monday). >> >> I will continue my work next week. > > This week will see some of it committed, thanks already. That's great news. Thanks :) > Do please let us know if/when you have a completely ports-based GitLab installation running. Currently there are 5 missing patches/new ports left to switch to completely port-based GitLab. I document the progress here: http://ports.toco-domains.de/gitlab-gem-dependencies.html > I tried that last year, but noticed some problems (e.g. with creating projects > via WebUI that'd eventually make its way into the filesystem) At the moment i have much to do; but i'm hopefully to test the completely port-based GitLab at the end of the week. At least my working schedule will allow me more work next week. :) Greetings, Torsten