Please find attached the files cm-2.4.0.ebuild, and ChangeLog. cm, or Common Music, is an object oriented music composition environment written in LISP. It is designed to be portable over a number of different LISP/scheme environments, and I have included support for generating a script for guile which autoloads the source packages for the user. I suggest this package goes under media-sound/cm.
Created attachment 8725 [details] cm-2.4.0.ebuild source file
Created attachment 8726 [details] Initial change log for media-sound/cm
I took a quick look at this and noticed that there are a bunch of warning during the install. The cm executable doesn't appear to get installed either. I'll work on fixing it up but it might be quicker if you take another look...
The cm executable is installed as a hard link to the file /usr/share/cm/bin/cm which is generated during the package install. It only creates it for guile at the moment, which might be what you think are warnings, unless you are getting warnings that I didn't during my development of the ebuild. I just looked at the CONTENTS file and it does look like /usr/bin/cm is not listed in there. That's because the package needs to create the cm executable after the package is installed, and then it installs. It then removes it in the pkg_prerm function. Like I said this only attempts to build the executable when the guile USE flag is set, so if you don't have that on it would not install the binary. I couldn't figure out how to fix this as there are no other use flags for the other supported lisps and I am unsure of how I can check if packages are installed that aren't specified in USE.
Seeing as it doesn't actually work with out guile it's not really a USE flag dep, more of a hard dep. It also needs >=guile-1.5, the guile-1.5.4 in portage doesn't build for me. I created a new ebuild for guile-1.6.3 and that got me to the point where i can run /usr/bin/cm. Need to carry on cleaning up the ebuild and committing a working version of guile.
Commited, it's ~x86 masked, as is guile-1.6.4, so you'll have to emerge it by hand or use ACCEPT_KEYWORDS. Feedback on how well it works would be greatly appreciated - if there is some simple way of testing the install please let me know! Thanks for the submission.
