Kenny Tilton writes:
And the good news is that they do not undergo evolutionary development over time, so they can just be replicated into a serious module and forgotten.
Well, yes. But if everything's already using Cells, it can't hurt to put it there. Unless you plan on releasing a major Cells-free package, in which case I guess it would want its own copy.
hmmmm. well, if we are going to upset the applecart we may as well do it all at once:
cells out from under cell-cultures to be a toplevel module in the cells project (and eventually the only one). hello-c into its own c-l.net project (if c-l.net approves) utils-kt replicated redundantly into... uh-oh. who exports it?! <sigh> OK, let's have cells export those functions. cello back over to the cello project cell-cultures sleeps with the fish
all those in favor? opposed?
I'd like to see utils-kt go in a cells/utils-kt subdirectory, but keep its own package. That way there's only one point in cvs to keep up-to-date, and Cello and cells-gtk can use it, but Cells users don't have to.
Weekend before last, I was going to put the new asdf-installable Cells release up on c-l.net, but I've managed to forget my gpg password, so I can't sign it. If it doesn't come to me over the next little while, I'll give up and make a new key.