<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><tt>On 04/10/2013 11:21 PM, Jeffrey
Ollie wrote:</tt><tt><br>
</tt></div>
<tt><br>
</tt>
<blockquote
cite="mid:CAD-DQxQhfFkPgB18ZM1dU82EKBUG-stLs_GwY2W18HVrhNQSaA@mail.gmail.com"
type="cite">
<pre wrap="">
2) Of the Ruby gems that _are_ packaged, many of them are the wrong version.
</pre>
</blockquote>
<tt>Yeap! Using </tt>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<tt><a href="http://www.isitfedoraruby.com/stats/gemfile_tool">http://www.isitfedoraruby.com/stats/gemfile_tool</a></tt><tt>
I was able </tt><tt><br>
</tt><tt>to see this.</tt><tt> </tt><tt>Some dependencies of Gitlab
are also fro</tt><tt>zen to </tt><tt>some previous version.</tt><tt><br>
</tt><tt>See </tt>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<tt><a href="https://gemnasium.com/gitlabhq/gitlabhq">https://gemnasium.com/gitlabhq/gitlabhq</a></tt><tt><br>
</tt>
<blockquote
cite="mid:CAD-DQxQhfFkPgB18ZM1dU82EKBUG-stLs_GwY2W18HVrhNQSaA@mail.gmail.com"
type="cite">
<pre wrap="">
3) For some of the Ruby gems that GitLab requires, it requires git
snaphots of non-released versions,or versions that have been
forked/patched by GitLab developers.
</pre>
</blockquote>
<tt>That is also true</tt><tt> and could be cumbersome to package.<br>
</tt>
<blockquote
cite="mid:CAD-DQxQhfFkPgB18ZM1dU82EKBUG-stLs_GwY2W18HVrhNQSaA@mail.gmail.com"
type="cite">
<pre wrap="">
4) I'm not sure GitLab releases tarballs, as the install instructions
refer to checking out git branches, even for the stable release
branch.
</pre>
</blockquote>
<tt>Luckily, they use tags </tt><tt><br>
</tt>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<tt><a href="https://github.com/gitlabhq/gitlabhq/tags">https://github.com/gitlabhq/gitlabhq/tags</a></tt>
<blockquote
cite="mid:CAD-DQxQhfFkPgB18ZM1dU82EKBUG-stLs_GwY2W18HVrhNQSaA@mail.gmail.com"
type="cite">
<pre wrap="">
5) There's no ability to fork a project from the web interface, and
thus have GitLab track merge requests. There's some upstream work on
implementing this feature but all of the patches that I saw had been
rejected. Personally, I feel that this is a big show-stopper as it's
one of GitHub's best features and why it has become so popular.
</pre>
</blockquote>
<tt>I want to believe that at some point this will be implemented.
Gitlab has gained<br>
a lot of supporters the past year and the project is constantly
evolving. Same goes<br>
with the repositories' public access that Kevin brought up in his
previous mail.<br>
</tt>
<blockquote
cite="mid:CAD-DQxQhfFkPgB18ZM1dU82EKBUG-stLs_GwY2W18HVrhNQSaA@mail.gmail.com"
type="cite">
<pre wrap="">
6) I have pretty decent systemd service files for GitLab, let me know
if you want 'em.
</pre>
</blockquote>
<tt>That would be great, thanks! Email me or contact me via github
:)</tt><tt><br>
</tt>
</body>
</html>