Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 06 May 2015 10:26:58 +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-KY60Mn9kRL@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 #4 from Torsten Z=C3=BChlsdorff <ports@toco-domains.de> ---
It's possible to install all rubygems only with the rubygem tool and comple=
tely
without pkg.

I've wrote about this topic with xmj@. I will quote him, because that's why=
 i
do the things this way:

=3D=3D=3D Start =3D=3D=3D
GitLab comes with an unmanageable amount of dependencies, which (as per rub=
y@
policy) may not be installed via bundle, and have to be (or become, if not =
yet
available) ports themselves. Using ``bundle`` is taboo mostly because libra=
ries
thus installed don't register with pkg, and can't be deinstalled properly u=
sing
that tool either.
=3D=3D=3D End =3D=3D=3D

For me this is very convincing. Also it comes with the advantage, that we c=
an
provide binary-packages for pkg, which currently works.

The GitLab port itself would be great. More than 100.000 organizations uses
this software. And it is relatively hard to install and maintained. The
FreeBSD-Ports tree offers a very simple method for this (compared to others=
).
And it allows freedom. There are just a few gitlab-packages in other
distributions and most of them comes with a full software-stack you cannot
change.=20
Even the possibility to change the software-stack is enough for my company =
to
sponsor some working-time at the project and considering the use of FreeBSD.
Normally the use Ubuntu and nothing else.

--=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-KY60Mn9kRL>