Re: [MacPerl] Another call for code!

[Kevin van Haaren <kevinv@sound.net>]

I'm curious about what should be submitted.  For example, I have 3 scripts
I use a lot: a droplet to convert perl scripts dropped on it to a droplet;
a droplet to convert perl scripts dropped on it to Mac CGI's; and a droplet
to convert Unix end-lines to Mac end-lines (stealing code from MP&E CD 8-).

All use a Module I wrote that allows folders to be dropped on them and the
scripts will walk the tree(s) and convert all files in the folders and
sub-folders.

The first 2 use either a blank CGI or blank droplet to push the text from
the data fork of the script into the resource fork.

Should the module I wrote be included with each script submission?

I believe on CPAN the standard is to use tar and gzip to make
distributions, I don't think (but I've been wrong many a time before 8-)
this supports resource forks. How should I submit the scripts that use the
resource fork only blank CGI/droplet files for templates?  Also is a make
script required?

Kevin

At 11:26 AM -0700 8/12/1998, Vicki Brown wrote:
>MacPerl (and MacPerl: Power and Ease ;-) were given a nice review in the
>WebAdmin column of WebServer Online magazine, July 1998, "Power to the
>People" (at http://webserver.cpg.com/wa/3.7/).
>
>The bad news is that they think our examples were more minimal and abstract
>than the reviewers would have liked; they wish we had more practical,
>complete examples. sigh.
>
>Then again, that's the big topic for the next book (if we do the sequel ;-).
>
>In the interim, this reminds me that the CPAN scripts directory has been
>effectively offline for a looonngg time, and I'd really like to see a
>shared repository of Perl (in particular, MacPerl!) scripts, code
>fragments, examples and the like.
>
>So once again, I'd like to request your help.  If you've written a script,
>please submit it to the MacPerl pages; we've got a submission form online
>at http://freebie.cfcl.com/macperl/depts/share.html. Feel free to include
>the code in the message, or just a URL. The code doesn't have to be
>"finished", either.  Almost anything could be useful.  We'll even accept
>modules (preferably MacPerl-specific modules or Mac ports of existing Perl
>modules).
>
>We'll try to get an ftp upload system working Real Soon.
>
>To forestall everyone who is about to tell me that this is what the CPAN is
>for ...
>
>   1) As I said, the CPAN scripts archive is, shall we say, not maintained
>at present.  I have considered volunteering to work on this; I may
>volunteer; but first, let's get a bunch of MacPerl scripts together.
>
>   2) Not everyone considers their stuff to be ready for publishing to CPAN
>as available modules!  We can provide a MacPerl community service; I'm as
>interested in unfinished modules as in everything else.  Let's use the
>Bizaar method of creating code; by the time it's ready for the CPAN, it
>will have been checked out here.
>
>I'm not advocating we don't use the CPAN or that the CPAN doesn't do its
>job.  But I think there's room for a centralized location on the way to the
>CPAN.  Even if we can just gather the URLs to various people's personal
>code repositories, we'll all gain.
>
>- Vicki
>---
>Vicki Brown, vlb@cfcl.com        |\      _,,,---,,_
>Journeyman Sourceror      ZZZzz /,`.-'`'    -.  ;-;;,_
>Scripts & Philtres             |,4-  ) )-,_. ,\ (  `'-'
>http://www.cfcl.com/~vlb      '---''(_/--'  `-'\_)
>P.O. Box 1269 San Bruno, CA  94066
>
>***** Want to unsubscribe from this list?
>***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch