A warning: I'm a noob, to both Scheme and Snow.
First question.
I have a snowball of pregexp[1] just about ready to upload, and I was wondering what would be appropriate to put as 'license:' ? Its license states: ----- Copyright (c) 1999-2005, Dorai Sitaram. All rights reserved.
Permission to copy, modify, distribute, and use this work or a modified copy of this work, for any purpose, is hereby granted, provided that the copy includes this copyright notice, and in the case of a modified copy, also includes a notice of modification. This work is provided as is, with no warranty of any kind. -----
I'm not sure how picky license: is. Would (license: bsd/mit-like) be ok? Something more descriptive? I'll probably email Dorai and ask if they'd prefer to maintain it or sign it as well before I upload the snowball. Probably be good to ask them what a good description of the license as a symbol would be too.
OK, next question.
How the heck do I use snow from a REPL o_O
Let's say I have this in an emacs buffer: ----- (package* test/v1.0.0 (require: time/v1))
(display (current-time-seconds)) -----
I hit C-c C-l to load and eval it, and it says current-time-seconds is undefined? If I instead slap ":";exec snow -- "$0" "$@" on top and run it as a snow script from a command line, it does what I'd expect it to do. Same results with MzScheme and Chicken so far. I cannot for the life of me figure out why it'd work one way and not the other, I assume I'm doing something fundamentally wrong.
Last question. For now ;)
What exactly are the differences between these?: load-program* include-program* load* include* include*-cd
Only include* seems to be documented, as far as I can tell. I suspect one of the -program* variety may resolve the REPL issue above, but I can't quite seem to penetrate the code.
And a suggestion:
It'd be nice if the docs mentioned that if you're using a *BSD, you probably want to use gtar when creating snowballs. I was racking my brain for a while on that one. Using NetBSD's default tar at least, seems to confuse snowman when it tries to unpack the snowball saying something about invalid filenames.
More docs for the various loads and includes would be handy as well. I'd be willing to document them, if I understood them.
Afficher les réponses par date
On Wed, Feb 20, 2008 at 07:24:12PM -0600, Matthew Martin wrote :
I'm not sure how picky license: is. Would (license: bsd/mit-like) be ok? Something more descriptive?
Or perhaps a link to a file inside the snowball, where this full header is, plus whatever compatible license you want to couple it with.
And a suggestion:
It'd be nice if the docs mentioned that if you're using a *BSD, you probably want to use gtar when creating snowballs. I was racking my brain for a while on that one. Using NetBSD's default tar at least, seems to confuse snowman when it tries to unpack the snowball saying something about invalid filenames.
All my computers run FreeBSD, and I never had any issue with snow and tar. One solution could be a snow package that builds others, with a simple tar embedded.
Adrien
On Thu, Feb 21, 2008 at 4:31 AM, Adrien Pierard pierarda@iro.umontreal.ca wrote:
On Wed, Feb 20, 2008 at 07:24:12PM -0600, Matthew Martin wrote :
I'm not sure how picky license: is. Would (license: bsd/mit-like) be
ok?
Something more descriptive?
Or perhaps a link to a file inside the snowball, where this full header is, plus whatever compatible license you want to couple it with.
A link how? Like (licence: COPYING) ? I was just using the license it came with, with the notice of modification it requires.
And a suggestion:
It'd be nice if the docs mentioned that if you're using a *BSD, you
probably
want to use gtar when creating snowballs. I was racking my brain for a while on that one. Using NetBSD's default
tar
at least, seems to confuse snowman when it tries to unpack the snowball saying something about invalid filenames.
All my computers run FreeBSD, and I never had any issue with snow and tar. One solution could be a snow package that builds others, with a simple tar embedded.
Gnu tar has a couple small derivations to the ustar format, I'd assume FreeBSD tar -c follows them. In tar/v1.0.1/snow/tar.scm I found this: ----- (define tar-format 'gnu) ;; can be gnu, ustar or v7 ;; (define tar-format 'ustar) ;; (define tar-format 'v7) ----- It would seem the "fix" would be to make it figure out which to use automatically when unpacking, which shouldn't be that difficult. If I get around to doing it and manage to not completely break things in the process, I'll send a patch for tar/v1 to Marc. But then I'm lazy, and just using gtar to build them works if you're doing it manually, or building them through snowman of course works fine.
Adrien
-- "I am not a Church numeral; I am a free variable!" (The Scheme Underground) For every complex problem, there is a solution that is simple, neat, and
wrong.
Snow-users-list mailing list Snow-users-list@iro.umontreal.ca Snow-users-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/snow-users-listhttps://webmail.iro.umontreal.ca/mailman/listinfo/snow-users-list
Also, The different loads and includes still confuse me, but not as much as before. From what I can tell, include* is like load* except you still have access to any macros which were in the file included. And the ones ending in -program* seem to be expecting a snowball package*. I'll get them figured out eventually.
load-program* was what I needed. Still not entirely sure why that works for me and include-program* doesn't seem to... oh well. Maybe next weekend I'll just make a (big) pot of coffee and and go through all of snow.scm's code and try to understand it better. For now, I have it doing what I needed.
As for pregexp, I still havn't heard back from Dorai. I'll give it about a week, if I still havn't gotten a response I'll just go ahead and upload what I have with something like (license: see-COPYING). Will that be OK?
snow-users-list@iro.umontreal.ca