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

Remove dependence on Versionomy #194

Closed
MaciekChudek opened this issue Aug 31, 2015 · 2 comments
Closed

Remove dependence on Versionomy #194

MaciekChudek opened this issue Aug 31, 2015 · 2 comments

Comments

@MaciekChudek
Copy link

Currently neither versionomy, nor one of it's dependencies, blockenspiel, are in either the official Arch repos or the AUR (Arch User Repos). This makes vmail a serious pain to install on Arch, at least for those commited to Arch's packaging system.

I'm keen to maintain a vmail AUR package, to make vmail more accessible to Arch users, but don't especially want to have to maintain versionomy and blockenspiel packages too. It looks like currently versionomy is only used once, to check that the ruby version is >= 1.9.0, in vmail.rb. Can we just do this check by hand and ditch versionomy? Happy to submit a pull request to this effect.

@notalex
Copy link
Collaborator

notalex commented Aug 31, 2015

@MaciekChudek, we recommend the rubygems package manger for installing Vmail. It makes it easier for us to maintain the dependencies.

However, we can remove versionomy. I don't see it adding any value in the way it is being used now.

@MaciekChudek
Copy link
Author

Great, thanks.

There are some pretty compelling reasons to stick with a single package management scheme, especially pacman under Arch. Upgrading, dependency tracking, uninstalling, migrating, etc., all become far easier and less likely to break things. But more importantly, by ditching versionomy it'll be possible for Arch users to go from zero to fully iinstalled vmail with a single command (or maybe two if they're fussy). Everyone loves convenience :-)

@notalex notalex closed this as completed Sep 4, 2015
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

2 participants