On Tue, Mar 27, 2012 at 7:48 PM, Jeremy Wall <jw...@google.com> wrote: > I would hesitate to require yi to be able to clone a git location. > This feels like a bad idea to me. > Having yi understand where the modules are located though that seems > reasonable. Hackage > integration might also be reasonable. How feasible would it be to do > use Hackage as a sort > of elpa (from emacs) for yi?
OK. I'll avoid the requirement on having a git clone. How about this instead: * The yi executable compiles custom yi using the Yi modules either in: 0. The package of the core Yi modules as well as GUI frontends. 1. A directory the user specifies. This could be a developers git clone. This should retain the functionality we have now as well as support the developer usage I'd like. A developer can compile custom yi without installing the Yi modules as a package. As for integrating package management and the hackage repo. Integrating with hackage is fairly reasonable. cabal2nix demonstrates automatic package data and metadata retrieval from hackage. I haven't tried integrating with Cabal for managing the ghc package database. -- Yi development mailing list yi-devel@googlegroups.com http://groups.google.com/group/yi-devel
