> With regard to everything else I think nothing speaks against > *extending* lyp to support arbitrary directories as well.
lyp already supports installing packages from local files. lyp install mypack:~/mypack-repo This feature can be used also for package development. > The Git > approach isn't absolutely crucial to lyp's internal working (IIUC) but > is the foundation for a number of its features. I'm sure there will be a > suitable way to support other types of packages, with less features. Git is only used for the process of installing packages: lyp clones the git repository, checks out the correct version, then copies the files to ~/.lyp/packages. As I wrote in the other message, lyp doesn't even require having git installed on your machine. It uses gitlib2 with ruby bindings. Sharon Rosner -- View this message in context: http://lilypond.1069038.n5.nabble.com/lyp-a-Package-Manager-for-Lilypond-tp186597p186623.html Sent from the User mailing list archive at Nabble.com. _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
