Re: [tbnl-devel] New macro: create-groups-bind-regex-dispatcher
On Wed, 31 Aug 2005 23:34:33 -0400, Bob Hutchison <hutch@recursive.ca> wrote:
Maybe a contributions directory? If this stuff isn't kept with TBNL I don't know how anyone is going to find it.
That's a good idea. So, to you and Alceste and whoever else wants to contribute I propose the following: Send me a tarball containing your contribution. All the stuff should be in one directory (pick a name you like) and should probably include a README file and some docs as you see fit. Don't forget to add suitable copyright notes and licenses for the lawyers. I'll add these directories to a 'contrib' directory and make a new TBNL release. Is that OK for you? Cheers, Edi.
On Sep 1, 2005, at 4:20 AM, Edi Weitz wrote:
On Wed, 31 Aug 2005 23:34:33 -0400, Bob Hutchison <hutch@recursive.ca> wrote:
Maybe a contributions directory? If this stuff isn't kept with TBNL I don't know how anyone is going to find it.
That's a good idea. So, to you and Alceste and whoever else wants to contribute I propose the following: Send me a tarball containing your contribution. All the stuff should be in one directory (pick a name you like) and should probably include a README file and some docs as you see fit. Don't forget to add suitable copyright notes and licenses for the lawyers.
I'll add these directories to a 'contrib' directory and make a new TBNL release.
Is that OK for you?
Sounds good to me.
Cheers, Edi. _______________________________________________ tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel
---- Bob Hutchison -- blogs at <http://www.recursive.ca/hutch/> Recursive Design Inc. -- <http://www.recursive.ca/> Raconteur -- <http://www.raconteur.info/>
Il giorno gio, 01/09/2005 alle 10.20 +0200, Edi Weitz ha scritto:
So, to you and Alceste and whoever else wants to contribute I propose the following: Send me a tarball containing your contribution. All the stuff should be in one directory (pick a name you like) and should probably include a README file and some docs as you see fit. Don't forget to add suitable copyright notes and licenses for the lawyers.
I'll add these directories to a 'contrib' directory and make a new TBNL release.
Is that OK for you?
It's fine for me (private email follows). As a side question: how are developers expected to use the contrib stuff? Should they cut'n'paste the source code, or is it going to be exported some way via asdf? (e.g. with a tbnl-contrib package, or something like that). (I hope it's not a silly question, please bear with the newbie :-) Regards, alceste -- Alceste Scalas <alceste.scalas@gmx.net>
[ Sorry, I can't seem to hit the reply-to-all button -- maybe senility setting in or the new icons on Mail.app don't work for me ] On Sep 5, 2005, at 5:25 AM, Alceste Scalas wrote:
Il giorno gio, 01/09/2005 alle 10.20 +0200, Edi Weitz ha scritto:
So, to you and Alceste and whoever else wants to contribute I propose the following: Send me a tarball containing your contribution. All the stuff should be in one directory (pick a name you like) and should probably include a README file and some docs as you see fit. Don't forget to add suitable copyright notes and licenses for the lawyers.
I'll add these directories to a 'contrib' directory and make a new TBNL release.
Is that OK for you?
It's fine for me (private email follows).
As a side question: how are developers expected to use the contrib stuff? Should they cut'n'paste the source code, or is it going to be exported some way via asdf? (e.g. with a tbnl-contrib package, or something like that).
(I hope it's not a silly question, please bear with the newbie :-)
Hadn't thought of that. In some cases cut'n'paste might be appropriate. In my case, I use ASDF routinely for everything I do (it is so easy and the payoff is so big). Including one of the contrib files in my project ASDF is no big deal. So I don't think smaller contributions are an issue. If the contribution is multi-file then maybe it should come with an ASDF definition of its own? If it has its own dependencies then it should come with its own ASDF file. While on this theme, what about PACKAGE? It could come with its own package or maybe, Edi, you could provide something like a TBNL- CONTRIBUTIONS package? Sometimes it is going to have to be in a TBNL package I suppose. I don't know. Cheers, Bob
Regards,
alceste -- Alceste Scalas <alceste.scalas@gmx.net> _______________________________________________ tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel
---- Bob Hutchison -- blogs at <http://www.recursive.ca/hutch/> Recursive Design Inc. -- <http://www.recursive.ca/> Raconteur -- <http://www.raconteur.info/>
On Mon, 5 Sep 2005 07:43:53 -0400, Bob Hutchison <hutch@recursive.ca> wrote:
Hadn't thought of that. In some cases cut'n'paste might be appropriate. In my case, I use ASDF routinely for everything I do (it is so easy and the payoff is so big). Including one of the contrib files in my project ASDF is no big deal. So I don't think smaller contributions are an issue. If the contribution is multi-file then maybe it should come with an ASDF definition of its own? If it has its own dependencies then it should come with its own ASDF file.
I personally think the best solution would be that each contrib has its own .asd file which lists TBNL amongst its dependencies. That way it's pretty clear without further explanations how the contrib is to be loaded.
While on this theme, what about PACKAGE? It could come with its own package or maybe, Edi, you could provide something like a TBNL- CONTRIBUTIONS package? Sometimes it is going to have to be in a TBNL package I suppose. I don't know.
I'll add a TBNL-CONTRIB package to TBNL which 'uses' CL and TBNL. So you can use it or you can provide your own package as you like. Cheers, Edi.
On Mon, 05 Sep 2005 11:25:17 +0200, Alceste Scalas <alceste.scalas@gmx.net> wrote:
It's fine for me (private email follows).
Sorry for the delay. I've just released a new version which incorporates a 'contrib' directory with your entry that I have left unchanged except for putting the code into the newly-created TBNL-CONTRIB package. Here's the ChangeLog: Version 0.6.0 2005-09-08 Added TBNL-CONTRIB package Added contrib directory with first entry (from Alceste Scalas) Updated link to Bill Clementson's blog Don't redefine what's already there (for LispWorks) Download: <http://weitz.de/files/tbnl.tar.gz> Cheers, Edi.
participants (3)
-
Alceste Scalas -
Bob Hutchison -
Edi Weitz