Thanks for catching that, I did not realize my replies were not going to the mailing list. I've renamed the source file to cooperative.scm and made the necessary changes to the setup and release-info files. The release is now 0.1.1 and 0.1.0 has been removed from cooperative.release-info. Thanks for the feedback.
On Wed, Jun 15, 2016 at 12:46 PM, Mario Domenech Goulart < [email protected]> wrote: > Hello Robert, > > On Wed, 15 Jun 2016 12:33:35 -0600 Robert Smiley <[email protected]> > wrote: > > > Oh. I read a tutorial a while back which showed giving the code an . > > import.scm extension as a way of allowing one to easily import code > > from the current directory when testing, be it interpreted or > > compiled. I didn't realize that was abnormal. Should I change it to > > have the .scm extension instead? > > Yes, please. You can use -J to make csc generate the import library > (which is usually compiled too). Take a look at some eggs' .setup files > for examples. > > Also note that you'll either have to move the current tag or create a > new one. If you decide for the latter, please remove the 0.1.0 release > from .release-info. > > P.S.: your message was not sent to the mailing list. Don't know if it > was intentional or not. In any case, feel free to reply to the list. > > All the best. > Mario > -- > http://parenteses.org/mario >
_______________________________________________ Chicken-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-users
