https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287926
John Hein <jcfyecr...@liamekaens.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.freebsd.org/bu
| |gzilla/show_bug.cgi?id=2830
| |73
CC| |ruby@FreeBSD.org
--- Comment #12 from John Hein <jcfyecr...@liamekaens.com> ---
Matthias, it seems that adding dependencies on -gitlab flavors are going to
keep causing problems.
Please re-read bug bug 283073, comment 0 and bug 283073, comment 3.
Now that you have added a number of rubygem*-gitlab ports as run-time
dependencies for sysutils/vagrant, many other ports are now in conflict at
run-time, including but not necessarily limited to the following:
sysutils/rubygem-fluentd rubygem-logger & rubygem-logger-gitlab conflict
www/rubygem-rest-client rubygem-logger & rubygem-logger-gitlab conflict
security/metasploit multiple conflicts
As suggested in bug 283703, there has to be a better way to build gitlab if it
depends on special versions of some rubygem* ports.
Most of these rubygem*-gitlab ports are no different than their non -gitlab
flavors other than in name.
If gitlab needs its own unique rubygem* port, consider putting those gems in a
namespace that is private to gitlab.
This proliferation of rubygem*-gitlab ports that are not actually needed by
non-gitlab ports is not tenable.
Maybe this is a wider ruby question - how to support ports that require
conflicting versions of particular gems. Apologies if this has already been
discussed somewhere. ruby@ CC'd. Comments welcome.
--
You are receiving this mail because:
You are on the CC list for the bug.
