The reason for this is that our internal directory tree doesn''t quite
match
the tree that gets published to RubyForge. The process for pushing out the
sources includes the application of some transforms to file layout and to
certain files. This file was apparently missed, probably because it was
added during the run-up to RailsConf. The best way to make sure it gets
resolved is to file a bug report for it at RubyForge.
On Sun, Jun 1, 2008 at 1:18 PM, Brad Wilson <dotnetguy at gmail.com>
wrote:
> Is there a reason why the output path for the YAML project is:
>
> ..\..\..\..\..\Main\bin\Debug\
>
> rather than
>
> ..\..\build\debug\
>
> ? The latter tries to place binaries outside the checkout folder.
>
> --
> http://bradwilson.typepad.com/
> http://www.flickr.com/photos/dotnetguy/
> http://www.last.fm/user/dotnetguy/
> _______________________________________________
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/ironruby-core/attachments/20080601/74fbe1c8/attachment.html>