Mochabot log - CommonJS IRC channel: #commonjs on irc.freenode.net

2010-07-24:

[0:18] <DanielFriesen> Using ruby gems recently has made me aware of some things I would definitely want to put in a package manager if I get back to monkeyscript
[0:20] <DanielFriesen> Though firstly........ anyone who decides that something like `gem install BlueCloth` should work, when `gem install bluecloth` won't, and that to include the package in code you need to use `gem "BlueCloth"\nrequire "bluecloth"` (two completely different names) needs to be stabbed
[0:20] <DanielFriesen> ((And there are worse))
[0:22] <DanielFriesen> I have a case currently where I have to downgrade some of my gems because of some compatibility issues, the only apparent way I can get this to work is to install specific versions, and then uninstall the new versions
[0:24] <DanielFriesen> A feature I would have liked would be the ability to run a specific program logging package loads in a special format, take that format and tweak it turning it into a file pinning packages to specific versions, and then re-run the program with that file as an arg causing the package manager to load those specific versions
[1:10] <nrstott> gems was great before it had years of bagage
[1:10] <nrstott> I wonder if npm will be the same
[1:30] * DanielFriesen also wishes there was a nicer automated way to install rubygems... but considering ruby1.9 bundles it, there will probably never be such a thing for 1.8
[1:31] <DanielFriesen> I don't use the rubygems in apt, I let rubygems manage it's own updates like most people probably do
[1:32] <DanielFriesen> So installing rubygems entitles downloading a tarball from a url with a hardcoded version number, unpacking it, then running sudo setup.rb in the folder
[1:33] <DanielFriesen> Course, that doesn't lend itself very nicely to being automated by something like puppet without manually updating it with the newest version number
[1:34] <DanielFriesen> iirc python had a built in easy_install
[1:35] <DanielFriesen> If a language engine doesn't bundle it's own package manager and it's not expected that the user's package manager will play nicely with the package manager if it tries to install it, then IMHO the engine should bundle a dead simple installer that can easily install the package manager
[1:36] <DanielFriesen> Say `ruby-install http://production.cf.rubygems.org/rubygems/rubygems-latest.tgz`
[2:07] * DanielFriesen wonders if he should manage his puppetmaster as a puppet client to itself
[3:54] * DanielFriesen wants to stab the guy that marked this valid bug affecting him as invalid https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/3685-actionpack-235-gem-declares-incompatibility-with-rack-110
[5:40] <DanielFriesen> rotfl, this is a fun realization... small aws instances come with 1 core/cpu...... ^_^ the cheaper/lessram/smaller rackspacecloud servers come with 4 core/cpu
[5:40] <DanielFriesen> Yet another advantage
[5:41] <DanielFriesen> Though... it is a little disappointing to find out that my puppetmaster has already maxed out it's ram and is using swap
[5:42] <DanielFriesen> Although.... apparently voltaire (the server commonjs used to be on)
[5:42] <DanielFriesen> has maxed out BOTH it's larger ram and swap... though I don't know if that's just because of mongo
[5:53] <DanielFriesen> Hmm... kyou (the server commonjs is on) has about 80-90MB free and is using about the same ammount of swap
[12:08] <Wes-> Dantman: using swap is not necessarily bad. In fact, keeping stuff you're not using in memory is always bad; memory can be better used for other things. If you are worried about swap, you must measure your paging rate. If you are not paging (significantly), then there is no problem.
[23:23] <Dantman> Wes-, I know, my note was that minus buffers and plus caches the server had little spare memory... not as bad as voltaire though, that looks like it is using swap as memory since it's out

 

 

Logs by date :