Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use celluloid-culture as a gem #706

Closed
balasankarc opened this issue Mar 8, 2016 · 3 comments
Closed

Use celluloid-culture as a gem #706

balasankarc opened this issue Mar 8, 2016 · 3 comments

Comments

@balasankarc
Copy link

Hi,
I am part of the team that maintains the package of celluloid gem in Debian. Right now, all celluloid-* gems use 'culture/sync' in gemspec and many other files using a relative path (which,also uses a git submodule). It is extremely difficult to handle submodules when it comes to distribution of a software.

I saw celluloid-culture is available as a gem. So, can you switch over to using it as a gem (using require 'celluloid/culture) so that it makes the life of package managers easy?

@digitalextremist
Copy link
Member

Hello @balasankarc, we are in the process of removing culture as a submodule, and removing all the relative interdependencies you're noticing. Sorry for the trouble //

@anthraxx
Copy link

anthraxx commented Apr 4, 2016

Hi, just wanted to mention: thanks a lot. Just came around as I wanted to also ask for improvement as it really hurts packaging (I'm from Arch Linux).
However the current gem just seems to be a placeholder, or am I wrong? The important sync.rb is not inside it when i create the gem from the gemspec source so its about more then just use that require

@digitalextremist
Copy link
Member

Yes, in 0.17.5 / 0.18.0 ( the release after the one going out shortly, 0.17.4 ) this will be removed. Feel free to reopen this issue if it's still a problem after the submodule is removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants