senny/rvm.el

Outdated packages on marmalade-repo - offer to help

Closed this issue · 11 comments

purcell commented

Hi Yves,

I noticed the rvm package in marmalade-repo is very outdated. I maintain a bunch of packages there (see http://marmalade-repo.org/profiles/purcell) -- if it would be helpful to you, you could add me as an owner of the rvm.el package there, and I could upload snapshot versions.

Alternatively, I've assembled a few functions which make it easy to upload a git-tagged .el file to marmalade from within Emacs, which might make it more convenient for you to upload official releases: https://github.com/purcell/emacs.d/blob/master/init-marmalade.el

Cheers,

-Steve

rejeep commented

+1

purcell commented

Any word on this? I keep finding bugs in the rvm package, only to discover they've been fixed in the github version. As noted above, I can help if you like.

-Steve

senny commented

@purcell sorry to keep you waiting this long. I lost my credentials to the marmalade-repo. I contacted @nex3 to reset my password but haven't had any luck signing in. I'm sorry for the lost time finding already resolved issues and hope to be able to upload a new version soon.

purcell commented

No problem - I know @nex3's very busy. Anyway, let me know if I can help in any way.

-Steve

senny commented

I finally managed to reset my password and uploaded the latest version of rvm.el.

http://marmalade-repo.org/packages/rvm/1.2

@purcell can you check if the bugs you mentioned to are gone? I don't use package.el personally so I'm not sure if everything worked as expected. Thanks a lot.

purcell commented

Thanks Yves! That's great.

I should also take this opportunity to mention Melpa (to which I am contributing): http://melpa.milkbox.net/

It's a collection of package.el packages all built from SCM (or Emacswiki): unlike Marmalade, there are no user account issues, so simple pull requests are all it takes to add packages to the repo.

-Steve

purcell commented

(I mention Melpa because it finally makes package.el a practical way to install any upstream dependency, so it might convince you to give package.el a try.)

senny commented

@purcell thanks for the mention. I used package.el some time ago, switched to el-get because I did not find all the needed dependencies. I really was unhappy with el-get and now I'm back to using submodules. We are building an Emacs configuration framework (https://github.com/senny/e-max) where multiple people are responsible to keep the dependencies up-to-date and working. At the moment submodules are completely sufficient but I'll keep an eye on Elpa, Marmalade and Melpa.

purcell commented

@senny I also used el-get for a while, then went back to submodules + ELPA. More recently I've been busy packaging libs for Marmalade, because I think it's important that we all support (and improve) the package.el direction. Your e-max "bundles" look similar to the pieces of @technomancy's Emacs Starter Kit, which are standard ELPA-style packages.

It'd be great in the long term if everyone could settle on a single package system, because there are lots of very smart people doing different things right now, and the useful knowledge is getting diluted. It's true that package.el isn't perfect, but it's turning into a solid foundation with a very wide userbase.

(BTW, I'm working to add support for automatically building proper "release" (rather than snapshot) versions in Melpa, using tags.)

-Steve

senny commented

@purcell I'd love to share thoughts about the current state but I guess this ticket is the wrong place. I notices, that you didn't leave an e-mail adress on your github account. Please send me an e-mail and I'll try to share my thoughts on some of the points you made above.

purcell commented

Great - I'd love to hear your thoughts. I'm steve at sanityinc dot com.

-Steve