Sophia

Package manager for the Emily programming language (emilylang.org)

sophia's People

Contributors

Here are some thoughts on the current design.md:

"Storage":

Maybe a line for "list of other packages required by this one"-- this might not be needed in version 0, but it's a pretty necessary idea.

"Dependency Installation"

"If they are local dependencies they will install to .emilylocallibs in the project folder. If they are global dependencies then they will install to ~/.emilylibs"
What is the difference? How does it tell the difference?
I would like to request the "local sandbox" not be an invisible file. Maybe begin with an underscore because a package can't do that?

"Sophia dependency file"
I'm sorry, I do not quite understand this section. We can discuss on IRC.

"Sophia Commands"

I think what would be consistent with other dependency tools is if "install" were the default to install. i don't think I would guess "get". Also most dependency tools assume you want recursive fetch (the equivalent of getAll). Maybe instead of "get" and "getAll" it could be "install" for "install plus deps" and "install --one" for "install by itself" (actually, honestly, i don't think installing by itself should be legal-- if it actually does depend on those other things, then installing it by itself is breaking your install!)
Is "run" appropriate for sophia? I was just going to put the -m run version into emily itself.
Do you need an "update" for fetching the contents of the big meta repo? Normal install tools seem to have install, update, and upgrade commands.

Recommend Projects