Bringing GitLab in Fedora
by Axilleas Pipinellis
Hello dear list!
I am applying for this year's GSOC [0] and I would like to contribute by
bringing GitLab [1][2] in Fedora. For those that don't already know
GitLab, it is a Self hosted Git management software written on Ruby on
Rails, pretty much like github's interface (you can try a demo here [3]).
It is a ruby app with lots of dependencies and I think this is a great
opportunity to extend the list of packaged gems supported by Fedora. Let
alone the fact that with the momentum GitLab has gained (it is in the
top 50 most popular open source projects on github) it would be an asset
if Fedora had this packaged. Also, the core developer was more than
willing to help with the process [4].
I could use any help needed on packaging. I have already exchanged a
couple of mails with Vit Ondruch and he pointed me to a direction. In
fact I am in the middle of reading all the related stuff from the wiki.
So what are your thoughts? Any guidance, ideas or insights are very much
appreciated!
Regards,
Axilleas
PS. There is also the thought of deploying GitLab to git repositories on
fedorahosted.org, but that's irrelevant to this list.
[0] https://fedoraproject.org/wiki/GSOC_2013
[1] http://gitlab.org
[2] https://github.com/gitlabhq/gitlabhq
[3] http://demo.gitlabhq.com/
[4] https://groups.google.com/forum/?fromgroups=#!topic/gitlabhq/SQMDi-yyXmU
10 years
Proposal - location of LICENSE and README files
by Miroslav Suchý
Hi,
all rubygems put their README and LICENSE files in %{gem_instdir}. This is opposed to all other packages, which put such
files into %{_docdir}/%{name}-%{version}. And all users and developers expect those files in this directory. Of course
but ruby developers who expect them in %{gem_instdir}.
Therefore I propose to put into Ruby guidelines this scriplet to unify this behavior:
```
%install
mkdir -p %{buildroot}%{_pkgdocdir}
for docfile in README; do
mv %{buildroot}%{gem_instdir}/$docfile %{buildroot}%{_pkgdocdir}
ln -s %{_pkgdocdir}/$docfile %{buildroot}%{gem_instdir}
done
%files
%doc %{gem_instdir}/README
%doc %{_pkgdocdir}/README
```
and put this text into ruby guidelines:
```
All documentation files, which resides in %{gem_instdir}, should be moved to %{_pkgdocdir}. Symbolic link from
%{gem_instdir}/<moved file> to %{_pkgdocdir}/<moved file> should be created. This especially apply on README and LICENSE
files.
```
Obviously the choice is to have symlink from %{gem_instdir} to %{_pkgdocdir}. Or from %{_pkgdocdir} to %{gem_instdir}.
I choosed the first option as those doc files are not needed for runtime and IMO should not be located in %{gem_instdir}
and it should be located under /usr/share/doc as all other packages do.
Opinions?
--
Miroslav Suchy, RHCE, RHCDS
Red Hat, Software Engineer, #brno, #devexp, #fedora-buildsys
10 years, 1 month
Using Fedora Ruby
by Sayth Renshaw
I am learning Rails. Fedora has the best up to date Ruby and Rails packages.
When establishing a development environment should I be using Rbenv or Rvm
on Fedora of neither ?
Is there any good advice you could give would you use Postgres or Maria etc.
Thank You
Sayth
10 years, 1 month
Rails 4 update and dependent packages (aoelus, mongoid, openshift)
by Josef Stribny
Hi all,
I hope I finished listing all dependencies on Rails 4.0 in our feature page[1]. If you spot something missing, please let me know.
As you can see, some updates should be trivial, but some cannot be made at the moment:
* There are several packages, which depends on Ruby on Rails framework. All need to be tested an updated. These needs to be surely updated:
** rubygem-cucumber-rails (loosen the dep should be enough)
** rubygem-haml-rails to 0.4
** rubygem-simple_form to 3.0.0rc
** rubygem-delayed_job to 3.1.4
** rubygem-rubigen might need update (stated deps are ok though)
** rubygem-paranoia might need update (stated deps are ok though)
* Following gems don't support Rails 4.0 right now and would be broken by the update:
** openshift-origin-broker and any of rubygem-openshift-origin* gems might need to be updated and tested against Rails 4.0
** rubygem-aeolus* packages
*** upstream no longer maintains the project
** rubygem-audited-activerecord
** rubygem-mongoid (mongoid 4.0 is blocked by 10gen Ruby driver)
*** https://github.com/mongoid/mongoid/issues/3128
As for the Rails' dependencies, we have them all covered by now. JBuilder and sdoc are waiting to be reviewed.
So to say, we would have to wait quite some time for mongoid, aeolus is not going to be updated and OpenShift is slowly starting (hopefully) to support Rails 4.0.
The question is: when should we do the update? I would like to see Rails 4.0 in F20, but I am not sure if all the deps can be there at the same time.
Josef
[1] https://fedoraproject.org/wiki/Changes/Ruby_on_Rails_4.0
10 years, 1 month
rspec 2.14.x will hit rawhide
by Mamoru TASAKA
Hello, all:
I pushed rspec suite 2.14.x into rawhide tree, which should hit
rawhide buildroot within a few hours. Please try using new rspec.
Regards,
Mamoru
10 years, 1 month
Removing vendor dirs from rubygems
by Troy Dawson
Hi,
What is the best way to remove the vendor directories from rubygems?
Is there a macro for it?
The problem I keep having is that the vendor directory is in the gem.
And this is what we need to have in the %prep section
-----
%prep
gem unpack %{SOURCE0}
%setup -q -D -T -n %{gem_name}-%{version}
gem spec %{SOURCE0} -l --ruby > %{gem_name}.gemspec
%patch0 -p1
-----
The problem is that the gemspec get's built with the vendor directory.
So, no matter where I put the "rm -rf vendor/" I have to have either a
complicated sed on the gemspec, or a major patch, that has to be updated
each time I update the version of the gem.
Is there an easier way? Is there a macro I am missing?
Is there a non-complicated sed command that works?
Troy
10 years, 1 month
