From owner-freebsd-ports-bugs@FreeBSD.ORG Wed May 6 10:09:20 2015 Return-Path: Delivered-To: freebsd-ports-bugs@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 63FDFBDF for ; Wed, 6 May 2015 10:09:20 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 4DC6C1F25 for ; Wed, 6 May 2015 10:09:20 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t46A9KLd008204 for ; Wed, 6 May 2015 10:09:20 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 199820] [new port] www/rubygem-html-pipeline Date: Wed, 06 May 2015 10:09:20 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: ports@toco-domains.de X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2015 10:09:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D199820 --- Comment #2 from Torsten Z=C3=BChlsdorff --- Hello John, the "gitlab" port is a future port of the GitLab-Software which is similar = to GitHub. It's fair to say, that some of the added rubygem-ports have no value without the gitlab-port. Nearly every rubygem port with "gitlab" in its name is wit= hout value while the gitlab-port itself is missing. I get you're "to less information"-point. I falsely believed, that everythi= ng is clear, because i wrote it to the mailinglist and discuss the progress wi= th xmj@, ruby@ and mmoll@. I'm sorry about that. In short: the future port "GitLab" has an awful long list of dependencies. = At least it depends on 96 rubygems. There are missing gems and outdated gems. = I've documented all of them (with links to PRs) here: http://ports.toco-domains.de/gitlab-gem-dependencies.html At the moment we are in a testing stage. I'm trying to put all the dependen= cies together to make the work at the gitlab-port possible. I have a copy of the ports-tree where i'm working on. Therefore it is possi= ble to create "a big patch". But i didn't think this is useful. Many of the pat= ches have there own value, especially the updates of existing ports. --=20 You are receiving this mail because: You are the assignee for the bug.=