As an aside, "gem install djspiewak-buildr" probably works again. I've merged Assaf's fixes, and GitHub *claims* to be building things correctly. So, I haven't tried it, but I can't think of a reason why it wouldn't work.
Daniel On Feb 27, 2:39 pm, Christian Vest Hansen <karmazi...@gmail.com> wrote: > On Fri, Feb 27, 2009 at 6:47 PM, Daniel Spiewak <djspie...@gmail.com> wrote: > > > Correction: > > > git clone git://github.com:djspiewak/buildr.git > > git clone git://github.com/djspiewak/buildr.git > > Excellent. Got it installed. > > > > > Daniel > > > On Feb 27, 11:44 am, Daniel Spiewak <djspie...@gmail.com> wrote: > >> I was able to repeat the problem. I suspect that the issue is the way > >> in which GitHub is building its gems. I think Assaf (the lead dev for > >> Buildr) has implemented a workaround in some of the more recent > >> commits, but I haven't been able to merge with his master so I really > >> couldn't say. > > >> For the moment, the solution is to just clone the git repository and > >> build using rake. If you were able to get djspiewak-buildr to install > >> (as you did), then you should be able to just run the following: > > >> sudo gem uninstall djspiewak-buildr > >> git clone g...@github.com:djspiewak/buildr.git > >> cd buildr > >> rake install > > >> Note that there is no need to run rake under sudo, the install task > >> will handle that for you. > > >> Daniel > > >> On Feb 26, 7:59 pm, Daniel Spiewak <djspie...@gmail.com> wrote: > > >> > Crud. I suspect this is something weird with the way that the GitHib > >> > gem server works. I'll try to repeat the problem on Ubuntu as soon as > >> > I get back to my computer. In the meantime, you could try these > >> > commands: > > >> > sudo gem uninstall djspiewak-buildr > >> > sudo gem install djspiewak-buildr > > >> > Daniel > > >> > On Feb 26, 3:59 pm, Christian Vest Hansen <karmazi...@gmail.com> > >> > wrote: > > >> > > rowe:~$ buildr --version > >> > > /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:36:in > >> > > `gem_original_require': no such file to load -- buildr (LoadError) > >> > > from > >> > > /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:36:in > >> > > `require' > >> > > from > >> > > /opt/local/lib/ruby/gems/1.8/gems/djspiewak-buildr-1.3.4/bin/buildr:18 > >> > > from /opt/local/bin/buildr:19:in `load' > >> > > from /opt/local/bin/buildr:19 > >> > > rowe:~$ gem --version > >> > > 1.3.1 > >> > > rowe:~$ > > >> > > On Thu, Feb 26, 2009 at 10:30 PM, Daniel Spiewak <djspie...@gmail.com> > >> > > wrote: > > >> > > > I'm not sure what the File not found thing is all about, but you > >> > > > should still be ok (crazy gems). Try the following: > > >> > > > buildr --version > > >> > > > Daniel > > >> > > > On Feb 26, 3:16 pm, Christian Vest Hansen <karmazi...@gmail.com> > >> > > > wrote: > >> > > >> On Thu, Feb 26, 2009 at 6:17 PM, Daniel Spiewak > >> > > >> <djspie...@gmail.com> wrote: > > >> > > >> > Odd. Must be a problem with RubyForge. If you try again, does it > >> > > >> > work? > > >> > > >> I tried again at home and got quite a bit further. Maybe it was > >> > > >> just a > >> > > >> hiccup at rubyforge. > > >> > > >> However, I still see some questionable things in the output, and I > >> > > >> have yet to actually try it out (this is the first time I'm trying > >> > > >> out > >> > > >> buildr). Here in verbatim: > > >> > > >> rowe:~$ sudo gem install djspiewak-buildr > >> > > >> Building native extensions. This could take a while... > >> > > >> Successfully installed builder-2.1.2 > >> > > >> Successfully installed net-ssh-2.0.4 > >> > > >> Successfully installed net-sftp-2.0.1 > >> > > >> Successfully installed rubyzip-0.9.1 > >> > > >> Successfully installed highline-1.5.0 > >> > > >> Successfully installed rubyforge-1.0.1 > >> > > >> Successfully installed hoe-1.7.0 > >> > > >> Successfully installed rjb-1.1.6 > >> > > >> Successfully installed Antwrap-0.7.0 > >> > > >> Successfully installed rspec-1.1.4 > >> > > >> Successfully installed xml-simple-1.0.11 > >> > > >> Successfully installed archive-tar-minitar-0.5.2 > >> > > >> Successfully installed djspiewak-buildr-1.3.4 > >> > > >> 13 gems installed > >> > > >> Installing ri documentation for builder-2.1.2... > >> > > >> ERROR: While generating documentation for builder-2.1.2 > >> > > >> ... MESSAGE: Unhandled special: Special: type=17, text="<!-- HI > >> > > >> -->" > >> > > >> ... RDOC args: --ri --op > >> > > >> /opt/local/lib/ruby/gems/1.8/doc/builder-2.1.2/ri --title Builder -- > >> > > >> Easy XML Building --main README --line-numbers --quiet lib CHANGES > >> > > >> Rakefile README doc/releases/builder-1.2.4.rdoc > >> > > >> doc/releases/builder-2.0.0.rdoc doc/releases/builder-2.1.1.rdoc > >> > > >> (continuing with the rest of the installation) > >> > > >> Installing ri documentation for net-ssh-2.0.4... > >> > > >> Installing ri documentation for net-sftp-2.0.1... > >> > > >> Installing ri documentation for highline-1.5.0... > >> > > >> Installing ri documentation for rubyforge-1.0.1... > >> > > >> Installing ri documentation for hoe-1.7.0... > >> > > >> Installing ri documentation for Antwrap-0.7.0... > >> > > >> Installing ri documentation for rspec-1.1.4... > >> > > >> Installing ri documentation for archive-tar-minitar-0.5.2... > >> > > >> Installing ri documentation for djspiewak-buildr-1.3.4... > >> > > >> File not found: lib > >> > > >> rowe:~$ ruby --version > >> > > >> ruby1.8.7(2008-08-11 patchlevel 72) [i686-darwin8] > >> > > >> rowe:~$ > > >> > > >> A failure to generate the docs I can live with, but that "File not > >> > > >> found" line looks pretty suspect. > > >> > > >> > Daniel > > >> > > >> > On Feb 26, 10:58 am, Christian Vest Hansen <karmazi...@gmail.com> > >> > > >> > wrote: > >> > > >> >> Nice initiative! > > >> > > >> >> However, it the net-ssh dependency has problems: > > >> > > >> >> [cvh: ~]$ sudo gem install djspiewak-buildr > >> > > >> >> ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError) > >> > > >> >> timed out (http://gems.rubyforge.org/gems/net-ssh-2.0.4.gem) > > >> > > >> >> On Sat, Feb 21, 2009 at 10:33 PM, Daniel Spiewak > >> > > >> >> <djspie...@gmail.com> wrote: > > >> > > >> >> > I'm pleased to announce preliminary (and very experimental) > >> > > >> >> > support > >> > > >> >> > for the Clojure AOT compiler and REPL within Apache Buildr > >> > > >> >> > (http:// > >> > > >> >> > buildr.apache.org). At present, this support is only > >> > > >> >> > available within > >> > > >> >> > my Git fork available here: > >> > > >> >> > git://github.com/djspiewak/buildr.git > >> > > >> >> > More specifically, Clojure support is available within the > >> > > >> >> > "clojure" > >> > > >> >> > and "master" branches ("master" branch alone contains REPL > >> > > >> >> > support). > >> > > >> >> > It should be possible to install this particular version of > >> > > >> >> > Buildr by > >> > > >> >> > using the following commands, though I'm honestly not sure how > >> > > >> >> > up to > >> > > >> >> > date GitHub's gem repository is: > > >> > > >> >> > gem sources -ahttp://gems.github.com > >> > > >> >> > sudo gem install djspiewak-buildr > > >> > > >> >> > Once installed, Clojure support is activated in a project > >> > > >> >> > simply by > >> > > >> >> > storing your .clj scripts within the src/main/clojure > >> > > >> >> > directory. Note > >> > > >> >> > that the (ns) directive will need to match the subdirectory, > >> > > >> >> > otherwise > >> > > >> >> > compilation will fail. By default, every script is compiled > >> > > >> >> > to the > >> > > >> >> > target/classes directory. Namespaces are auto-detected from > >> > > >> >> > the > >> > > >> >> > directory structure. Only updated files are re-compiled > >> > > >> >> > (based on > >> > > >> >> > mtime of .clj file and its corresponding *__init.class). If > >> > > >> >> > you wish > >> > > >> >> > to override the auto-detection and specify a reduced set of > >> > > >> >> > namespaces, it can be done using the `compile.using` directive > >> > > >> >> > within > >> > > >> >> > your project definition in your buildfile. Thusly: > > >> > > >> >> > define 'clojure-contrib' do > >> > > >> >> > compile.using :libs => ['clojure.contrib.command-line', > >> > > >> >> > 'clojure.contrib.mmap'] > >> > > >> >> > end > > >> > > >> >> > Any scripts which are *not* pre-compiled will be copied > >> > > >> >> > verbatim to > >> > > >> >> > the target/classes directory w.r.t. their position in the > >> > > >> >> > directory > >> > > >> >> > structure. Note that you will need to have set CLOJURE_HOME > >> > > >> >> > for this > >> > > >> >> > to work. > > >> > > >> >> > You will have to be using the "master" branch from my git > >> > > >> >> > repository > >> > > >> >> > in order to use the Clojure REPL through Buildr (or install > >> > > >> >> > via the > >> > > >> >> > gem command given above). To invoke, simply run the following > >> > > >> >> > command > >> > > >> >> > somewhere in your project hierarchy: > > >> > > >> >> > buildr shell > > >> > > >> >> > This will launch the Clojure REPL pointing at your project's > >> > > >> >> > dependencies and the updated target/classes directory > >> > > >> >> > (compilation is > >> > > >> >> > re-run if necessary). Additionally, if you have a valid > >> > > >> >> > license for > >> > > >> >> > JavaRebel, you can make use of it with the REPL by setting the > >> > > >> >> > REBEL_HOME environment variable. > > >> > > >> >> > Note that you cannot mix Java and Clojure sources within the > >> > > >> >> > same > >> > > >> >> > project. > > >> > > >> >> Aww... :( > > >> > > >> >> > However, this is fairly easy to overcome by splitting the > >> > > >> >> > languages into separate sub-projects. Thus, your top-level > >> > > >> >> > project > >> > > >> >> > might contain all of your Clojure sources, while the > >> > > >> >> > sub-project might > >> > > >> >> > contain Java. There are more details regarding this process > >> > > >> >> > on the > >> > > >> >> > Buildr project page. > > >> > > >> >> > One thing to keep in mind is that Buildr was designed to serve > >> > > >> >> > as a > >> > > >> >> > build system for more static languages (specifically: Java, > >> > > >> >> > Scala, > >> > > >> >> > Groovy). Thus, it is pre-biased toward things like a separate > >> > > >> >> > compilation phase (the REPL points to target/classes rather > >> > > >> >> > than src/ > >> > > >> >> > main/clojure). > > >> > > >> >> > Fair warning: this language support is *extremely* > >> > > >> >> > experimental and > >> > > >> >> > probably not too reliable at this point. Also note that while > >> > > >> >> > it is > >> > > >> >> > possible that Clojure support will be merged into the Buildr > >> > > >> >> > trunk in > >> > > >> >> > future, it has not yet been decided one way or another (see > > ... > > read more » --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
