[Gitlab] Current Status of the port
Steve Wills
swills at FreeBSD.org
Fri Jul 31 14:40:02 UTC 2015
Hi,
On Fri, Jul 31, 2015 at 04:13:06PM +0200, Torsten Zuehlsdorff wrote:
>
> You was a little bit faster than me. Today i compiled a number of
> changes needed to get GitLab build. I've found some minor problems and
> fixed them too.
>
> You need 3 steps to get the ports-tree in the correct shape:
>
> 1. apply the attachment gitlab-portstree-patch.diff to /usr/ports/
> 2. save the attachment gitlab-with-dependencies.shar in /usr/ports/ and
> extract it
Awesome, thanks. The shar seems to include both the diff an older version of
the same shar. No worries tho. Glad it doesn't include the Makefile~ files that
the shars in bugzilla have. :)
> 3. get the most actual GitLab copy from
> svn://svn.toco-domains.de/freebsd-ports/www/gitlab
Seems identical to the one in the shar, as far as I can tell.
> Now you should be able to build GitLab. :)
Almost. Seems a patch to update devel/rubygem-gitlab_git to 7.2.5 (or newer?) is missing, maybe others:
===> gitlab-v7.13.2 depends on file: rubygem-gitlab_git-rails41>=7.2.5 - not found
> Please make sure, that there is no older or newer version of Rails is
> installed. I removed every Rubygem before testing to avoid conflicts.
>
> To setup GitLab follow the quide:
> https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/install/installation-freebsd.md
>
> I've created a basic working configuration for default. You just should
> change the "host" in config/gitlab.yml, if you want to use something
> other than "localhost". The rest should work. But please test carefully,
> i've done many changes in the last months.
>
> The part to setup the nginx vhost is currently missing. If you're
> familar with the setup, there will be no big problems. I did not see the
> default configuration for a long time; therefore i need to figure it out
> to adjust the guide. -.-
Ok, I was planning to build packages in poudriere and install those in a new
empty jail and use my existing proxy to proxy things to it.
> Yes. I run portlint on everything attached, but it throws 3 errors for
> every slave-port. If i fix there errors, the ports don't work. Here i
> need you're feedback what to do.
Need details on this.
Steve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 603 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-ruby/attachments/20150731/0d1c78e9/attachment.bin>
More information about the freebsd-ruby
mailing list