I'd like markaby to be a hard dependancy - it's the default, if it isn't installed beginners get terribly confused, and installing one more gem really isn't going to cause problems for people - computers have so much free space these days. If they really (for whatever reason) want to refuse markaby's inclusion, they can ask rubygems to bypass dependancies.
— Jenna Fox On Tuesday, 20 December 2011 at 8:26 AM, Magnus Holm wrote: > On Mon, Dec 19, 2011 at 21:34, Isak Andersson <icepa...@lavabit.com > (mailto:icepa...@lavabit.com)> wrote: > > > My suggestion would be to make it Markaby 2.0 (of course, once it's > > > running and mostly backwards-compatible), keeping the old gem name, > > > and to develop on a branch in markaby repo. > > > > > > > > > > > Yeah, we should more or less do a rewrite and make it properly open source. > > You are allowed to make something with the same name aren't you? I mean > > there > > is songs with the same names after all. > > > > So what we would have wouldn't exactly be Markaby but it would be used > > exactly > > like Markaby. We could make it smaller/faster and more up to date :) > > > > > Just so everyone knows: Camping doesn't depend on Markaby today. It's > only loaded when you actually try to use it. Would you suggest that we > switch to a hard dependency on Markaby, or should we continue what > we're doing today? > _______________________________________________ > Camping-list mailing list > Camping-list@rubyforge.org (mailto:Camping-list@rubyforge.org) > http://rubyforge.org/mailman/listinfo/camping-list > >
_______________________________________________ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
