[Date Prev][Date Next][Thread Prev][Thread Next] [Search] [Date Index] [Thread Index]

macperl-modules-digest V1 #7




macperl-modules-digest    Wednesday, March 10 1999    Volume 01 : Number 007




----------------------------------------------------------------------

Date: Mon, 8 Mar 1999 12:38:50 -0400 (AST)
From: Arved Sandstrom <Arved_37@chebucto.ns.ca>
Subject: [MacPerl-Modules] Question about PAUSE

I figure I've got PAUSE down, sort of. I had Bit::Vector all set, uploaded
that, checked it in, and saw that it was duly registered, the Readme
extracted, and so forth.

When I downloaded off /incoming to doublecheck, naturally enough I found
that the one thing I did manually (putting files in the proper places)
when assembling the distribution (when I could have done it automatically)
frigged up a file location for our Mac install procedures. So I used PAUSE
'delete', and that worked out OK.

Other than resolving to doublecheck a .tgz on my own machine with
'installme', before I upload, which I neglected to do for this one (of
course), I have another question - PAUSE evidently doesn't delete stuff
for 48 hours or so. So I have to assume that until Wednesday evening I
can't upload a fix? Correct? But after that it's OK?

Any wisdom and knowledge on this much appreciated.

Arved

P.S. I'm going to have to checklist this whole procedure, and automate it
some more. Between sticking original files where you want the ported ones
to go, and vice versa, and things of that nature, I'm finding a number of
things here that can derail a port or binary even though the 'blib' itself
is OK. (In this case everything else was Ok - I screwed up the 'blib'
tree. The original _did_ come from BuildProgram, but in the process of
testing.... Don't ask. :-))

I'm thinking of a 'make dist' equivalent, basically. Some of this
distribution editing is getting pretty old. :-)

Any tips or comments? Paul and Chris, you guys have done this a lot - you
use a checklist, or have some scripts in play? Just curious.




==== Want to unsubscribe from this list?
==== Send mail with body "unsubscribe" to macperl-modules-request@macperl.org

------------------------------

Date: Mon, 8 Mar 1999 12:09:41 -0500
From: Chris Nandor <pudge@pobox.com>
Subject: Re: [MacPerl-Modules] Question about PAUSE

At 11.38 -0500 1999.03.08, Arved Sandstrom wrote:
>Other than resolving to doublecheck a .tgz on my own machine with
>'installme', before I upload, which I neglected to do for this one (of
>course), I have another question - PAUSE evidently doesn't delete stuff
>for 48 hours or so. So I have to assume that until Wednesday evening I
>can't upload a fix? Correct? But after that it's OK?

You can upload a fix at any time, but you can never again upload a file of
the same name (without special dispensation from Andreas).  If you uploaded
"Bit-Vector-5.6-bin-1-MacOS.tgz", your next upload should probably be
"Bit-Vector-5.6-bin-2-MacOS.tgz".



>Any tips or comments? Paul and Chris, you guys have done this a lot - you
>use a checklist, or have some scripts in play? Just curious.

I do this:

1.  Copy a clean distribution folder
2.  Rename it to something like "Module-Foo-bin-1-MacOS" that fits in 27
    characters or less
3.  Create a new folder called Mac_changed inside it
4.  Take files I edited and move the originals to Mac_changed
5.  Copy my changed versions to where those files were
6.  Copy blib into the distribution folder
7.  (I have not done this yet, though I am going to start)
      7a. Make new folder called Mac_makefile
      7b. Copy Makefile.mk and *.makeout to Mac_makefile
8.  Add info to the top of the README

I suppose most of this could be automated.  A script could do the
following, given two paths (one for $new distribution folder, one for $port
folder).

1.  mkdir "$new:Mac_changed"
2.  mkdir "$new:Mac_makefile"
3.  find(sub {
        my $file = $File::Find::name;
        (my $pfile = $file) =~ s/^$new/$port/;
        unless (compare_files($file, $pfile)) {
            move($file, "$port:Mac_changed:");
            copy($pfile, $file);
        }
    }, $new);

    i.e., for each file in the new directory, move it to Mac_changed and copy
    the one in the port directory in its place if the files are not the same.

4.  copy_dir "$port:blib", $new
5.  copy "$port:Makfile.mk", "$new:Mac_makefile:"
6.  chdir $port; for (<*.makeout>) {copy $_, "$new:Mac_makefile:"}

Then just edit the README and make sure the directory is named well.  Seems
like that should all do the trick.

- --
Chris Nandor          mailto:pudge@pobox.com         http://pudge.net/
%PGPKey = ('B76E72AD', [1024, '0824090B CE73CA10  1FF77F13 8180B6B6'])

==== Want to unsubscribe from this list?
==== Send mail with body "unsubscribe" to macperl-modules-request@macperl.org

------------------------------

Date: Tue, 9 Mar 1999 08:28:01 -0500
From: Chris Nandor <pudge@pobox.com>
Subject: [MacPerl-Modules] Mac::Glue notes

Just a quick note here: I think I am going to change Mac::Glue to work like
this:

  use Mac::Glue;
  $f = new Mac::Glue 'Finder';

The Finder docs, instead of being stored in Mac:Glue:Finder.pm, will be in
Mac:Glue:Finder.pod, and the hash will be stored in a persistent data
structure using something else.  Probably stored in
"$ENV{MACPERL}site_perl:Mac:Glue:Appname", so it can be found reliably.
But that is up in the air.

I am thinking of using MLDBM and Storable and DB_File.  This will mean a
couple of things:

* Disk storage requirements go down
* Time to load goes down, since MLDBM does not require entire structure to
be read in at load time, which is good for huge aete's like for the Finder
* Storable needs to work on CFM68K and needs to be statically linked to
bigappl, eventually, if we want non-CFM68K 68K people to be able to use it
... I don't recall if Storable works on CFM68K now

Let me know if you see any problems with this.

Also, I am thinking of asking people who want to discuss Mac::Glue to join
this list.  Any problems with that?  Better place?  macperl-toolbox?
macperl?

- --
Chris Nandor          mailto:pudge@pobox.com         http://pudge.net/
%PGPKey = ('B76E72AD', [1024, '0824090B CE73CA10  1FF77F13 8180B6B6'])

==== Want to unsubscribe from this list?
==== Send mail with body "unsubscribe" to macperl-modules-request@macperl.org

------------------------------

Date: Tue, 9 Mar 1999 20:32:05 -0500
From: Larry Moore <ljmoore@freespace.net>
Subject: Re: [MacPerl-Modules] Mac::Glue notes

>At 15.19 -0500 1999.03.09, Larry Moore wrote:
>>>... I don't recall if Storable works on CFM68K now
>>>
>>Ok, boss ... how would I test that for you?
>
>
>:)  Just download the Storable archive off my CPAN directory and run the
>tests.  You will have to change some of test files from:
>    require 't/dump.pl';
>To:
>    require 'dump.pl';
>
>You can install it from CPAN shell, if you use it, with:
>
>    cpan> install CNANDOR/Storable-0.6@3-bin-2-Mac.tgz

All .t files pass syntax check.

canonical.t, forgive.t, tied.t all OK

dclone.t,
retrieve.t(at least one OK flashed)
	"finder" unimplemented trap

freeze.t does. freezes the system - no error messages

store.t "finder" error type 10 and froze.

Hope this helps.

- -
The world is one country and mankind, its citizens.

Larry Moore and Shirley Allan
Union Street West
Fergus ON Canada



==== Want to unsubscribe from this list?
==== Send mail with body "unsubscribe" to macperl-modules-request@macperl.org

------------------------------

Date: Tue, 9 Mar 1999 21:56:00 -0500
From: Chris Nandor <pudge@pobox.com>
Subject: Re: [MacPerl-Modules] Mac::Glue notes

At 20.32 -0500 1999.03.09, Larry Moore wrote:
>>At 15.19 -0500 1999.03.09, Larry Moore wrote:
>>>>... I don't recall if Storable works on CFM68K now
>>>>
>>>Ok, boss ... how would I test that for you?
>>
>>
>>:)  Just download the Storable archive off my CPAN directory and run the
>>tests.  You will have to change some of test files from:
>>    require 't/dump.pl';
>>To:
>>    require 'dump.pl';
>>
>>You can install it from CPAN shell, if you use it, with:
>>
>>    cpan> install CNANDOR/Storable-0.6@3-bin-2-Mac.tgz
>
>All .t files pass syntax check.
>
>canonical.t, forgive.t, tied.t all OK
>
>dclone.t,
>retrieve.t(at least one OK flashed)
>	"finder" unimplemented trap
>
>freeze.t does. freezes the system - no error messages
>
>store.t "finder" error type 10 and froze.
>
>Hope this helps.

Well, not really.  :)  Actually, it helps in that I can say that what I am
working on won't work on 68K systems until we get Storable working.

Although, I could just use DB_File or FreezeThaw for serializing for now.
FreezeThaw is all perl and should work on 68K systems (though you might
want to try it out).

- --
Chris Nandor          mailto:pudge@pobox.com         http://pudge.net/
%PGPKey = ('B76E72AD', [1024, '0824090B CE73CA10  1FF77F13 8180B6B6'])

==== Want to unsubscribe from this list?
==== Send mail with body "unsubscribe" to macperl-modules-request@macperl.org

------------------------------

End of macperl-modules-digest V1 #7
***********************************


==== Want to unsubscribe from this list?
==== Send mail with body "unsubscribe"
==== to macperl-modules-digest-request@macperl.org