Date: Wed, 06 May 2015 10:09:20 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 199820] [new port] www/rubygem-html-pipeline Message-ID: <bug-199820-13-fYhVYSi4So@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-199820-13@https.bugs.freebsd.org/bugzilla/> References: <bug-199820-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D199820 --- Comment #2 from Torsten Z=C3=BChlsdorff <ports@toco-domains.de> --- 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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-199820-13-fYhVYSi4So>