On Tue, Dec 17, 2013 at 3:15 AM, Nick Wellnhofer <[email protected]> wrote: >> Lucy's build will get a lot simpler if we make Clownfish an ordinary >> prerequisite. :)
> Yes, I'm really looking forward to this. It will make life a little harder > for developers who have to work with an up-to-date source tree of both > Clownfish and Lucy but this can be worked around by setting LIBRARY_PATH, > LD_LIBRARY_PATH, and PERL5LIB. Also, after simplification Lucy can serve as sample code for an elaborate Clownfish-powered library. >> Theoretically we could filter history for the new Charmonizer and Clownfish >> repositories, but I think things have moved around so much that the >> potential for data loss is too great. I suggest that we just clone the >> existing lucy.git repo and then edit down. > > If we clone the Lucy repo, the history of most of the Clownfish files will > include two move operations: > > * From core/Lucy to clownfish/runtime/core/Clownfish > * From clownfish/runtime/core/Clownfish to runtime/core/Clownfish > > It will be hard to track changes across these renames, so I think we could > as well start the Clownfish repo from scratch. Works for me. Charmonizer's history is reasonably straightforward, at least when you're looking at specific paths. There will be a lot of extraneous commits on master related to Lucy and Clownfish, but oh well. I'm fine with naming the Clownfish repository lucy-clownfish.git, even though the product will be "Apache Clownfish" and not "Apache Lucy Clownfish". We'll cross the TLP bridge when we come to it. Likewise with the Charmonizer repo being named lucy-charmonizer.git. With Charmonizer, there are not even any plans as of yet to release the full product independently. Marvin Humphrey
