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

macperl-modules-digest v01.n004



From: owner-macperl-modules-digest@macperl.org (macperl-modules-digest)
To: macperl-modules-digest@macperl.org
Subject: macperl-modules-digest V1 #4
Reply-To: macperl-modules@macperl.org
Sender: owner-macperl-modules-digest@macperl.org
Errors-To: owner-macperl-modules-digest@macperl.org
Precedence: bulk


macperl-modules-digest    Wednesday, March 3 1999    Volume 01 : Number 004




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

Date: Wed, 3 Mar 1999 06:13:19 -0400 (AST)
From: Arved Sandstrom <Arved_37@chebucto.ns.ca>
Subject: Re: [MacPerl-Modules] Other MMP stuff

On Tue, 2 Mar 1999, Chris Nandor wrote:

> I was thinking about this the other day, and it came up with XML::Parser.
> What to do to check out a new version of an existing module?  Maybe I
> should have a separate column for "download", where you can get the
> existing port?  So even if nothing is in the "done" column, you could
> download an old version if present.

I saw that issue as soon as I caused it. :-) I wasn't too worried about it
because the availability of the existing port (through the MMP page) is
only going to be affected for a few days, and I don't get the impression
that masses of people are downloading XML::Parser (could be wrong - just
don't know). A proper solution would be nice, though.

Maybe an extra download column, just as you describe, which is headed
DOWNLOAD (VERSION), and the link text is the version number, so the
individual can see at a glance, hey, 2.20 is checked out and being worked
on, but if I were to download I'd get 2.19.

Arved



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

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

Date: Wed, 3 Mar 1999 06:20:44 -0400 (AST)
From: Arved Sandstrom <Arved_37@chebucto.ns.ca>
Subject: Re: [MacPerl-Modules] MMP

On Tue, 2 Mar 1999, Chris Nandor wrote:

> What do people think about making a link on the MMP page for people to send
> ideas for new modules to port/build and feedback on existing ports/builds,
> that would be sent to macperl-modules@perl.org?
> 
Off the top of my head I don't know why this traffic shouldn't come to
macperl-modules. It's a natural place for it.

I'll be happy with *anything* that makes it a bit easier (read convenient)
for people to send comments about builds (new ideas and feedback). Right
now I'm starved for info about what's going on with my builds posted on
MMP. Admittedly there are only two at the moment, but one (XML::Parser)
carries extra significance because it's the linchpin for many others.

I'd like to know whether people are finding other Mac-related bugs as they
use it. I'd like to know, period, how many folks _are_ using it. :-) And,
of course, I'd really like to know - how is it doing on CFM68K?

Arved



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

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

Date: Wed, 3 Mar 1999 08:28:58 -0500
From: Chris Nandor <pudge@pobox.com>
Subject: Re: [MacPerl-Modules] Other MMP stuff

At 05.13 -0500 1999.03.03, Arved Sandstrom wrote:
>Maybe an extra download column, just as you describe, which is headed
>DOWNLOAD (VERSION), and the link text is the version number, so the
>individual can see at a glance, hey, 2.20 is checked out and being worked
>on, but if I were to download I'd get 2.19.

Good idea.  I am going to do this.  And add a new field.

I am going to also change the field for main distribution link to
distribution name, which will not be displayed but used to link to CPAN
Testers.  If not present, module name will be used.  This will currently
affect:

  Devel::DProf (DProf)
  LWP (libwww-perl)
  Math::Random (MathRandom)

I guess I will add one more column in the table, for the link to CPAN
Testers.  Current version won't link to anything.  I was thinking about
making the version link to CPAN Testers, but that doesn't make much sense,
I don't think.

I'm also going to shorten the dates to dd.mm.yy (the table is a bit wide).
The dates are stored internally in seconds, so I don't care about y2k
problems on the page.

- --
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: Wed, 3 Mar 1999 08:30:54 -0500
From: Chris Nandor <pudge@pobox.com>
Subject: Re: [MacPerl-Modules] MMP

At 05.20 -0500 1999.03.03, Arved Sandstrom wrote:
>On Tue, 2 Mar 1999, Chris Nandor wrote:
>
>> What do people think about making a link on the MMP page for people to send
>> ideas for new modules to port/build and feedback on existing ports/builds,
>> that would be sent to macperl-modules@perl.org?
>>
>Off the top of my head I don't know why this traffic shouldn't come to
>macperl-modules. It's a natural place for it.
>
>I'll be happy with *anything* that makes it a bit easier (read convenient)
>for people to send comments about builds (new ideas and feedback). Right
>now I'm starved for info about what's going on with my builds posted on
>MMP. Admittedly there are only two at the moment, but one (XML::Parser)
>carries extra significance because it's the linchpin for many others.
>
>I'd like to know whether people are finding other Mac-related bugs as they
>use it. I'd like to know, period, how many folks _are_ using it. :-) And,
>of course, I'd really like to know - how is it doing on CFM68K?

I think I will put up a mail address for now, and a form for sending
feedback will be on my TODO list.

Assuming we can send mail from outside in.  I am going to try from another
address now and see what happens.

- --
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: Wed, 3 Mar 1999 08:36:29 -0500
From: Jennifer Nandor <jnandor@pobox.com>
Subject: [MacPerl-Modules] test

test

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

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

Date: Wed, 3 Mar 1999 08:46:40 -0500
From: Chris Nandor <pudge@pobox.com>
Subject: Re: [MacPerl-Modules] Other MMP stuff

At 08.28 -0500 1999.03.03, Chris Nandor wrote:
>I am going to also change the field for main distribution link to
>distribution name, which will not be displayed but used to link to CPAN
>Testers.  If not present, module name will be used.  This will currently
>affect:
>
>  Devel::DProf (DProf)
>  LWP (libwww-perl)
>  Math::Random (MathRandom)

Silly me ... cpan.perl.com has a find by distribution, so I can just use
distribution name for everything.  Though some people really might want to
know the module name.  But there might not be one module name.  I guess
we'll just use distribution name.  Most of the time the proper distribution
is obvious.

Distribution   libwww-perl                       Link to cpan.perl.com
Version        1.41                              No link
Author         GAAS                              Link to authors/00whois.html
Test           [bullet]                          Link to cpan-testers
Binary         [bullet] (none in this case :)    Link to info about binaries!
Download       1.41                              Link to port distribution
In             29.01.1999 / schinder             No link
Out            29.01.1999 / schinder             No link
Done           29.01.1999 / schinder             No link

I won't do this for several hours yet, so let me know if you have
suggestions or problems.

Hm.  Should we keep the link to the main distribution?  It really wouldn't
hurt anything.  Just extra info to download.

Actually, if the cpan.perl.com folks linked to CPAN Testers, we would not
need to link to CPAN Testers, either.  cpan.perl.com could be the one stop
shopping for all three links: distribution, documentation, and testing.
And a link would be very easy for them to do, since they already have the
distribution name.  I'll ask Eric Eisenhart about it.

- --
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: Wed, 3 Mar 1999 08:50:02 -0500
From: Chris Nandor <pudge@pobox.com>
Subject: Re: [MacPerl-Modules] test

At 08.36 -0500 1999.03.03, Jennifer Nandor wrote:
>test

OK, barring anyone voicing a problem today, I will add it to the MMP page.

- --
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: Wed, 3 Mar 1999 09:09:17 -0500
From: "Paul J. Schinder" <schinder@pobox.com>
Subject: Re: [MacPerl-Modules] Other MMP stuff

On Wed, Mar 03, 1999 at 08:46:40AM -0500, Chris Nandor wrote:
} 
} Hm.  Should we keep the link to the main distribution?  It really wouldn't
} hurt anything.  Just extra info to download.

Might be a good idea.  Currently I leave some stuff out of the port of
LWP, like the command line scripts that aren't easy to use under
MacPerl.  And the Archive::Tar port is just the Tar.pm file itself,
since the patch is going to be back in the next version and that line
will disappear anyway.

I'm in the process of reworking the LWP port distribution into a
.tar.gz installable from CPAN (if ever I find enough time when I'm
running MacOS), so I can put the excluded stuff back in if you think
it's a good idea.  Actually what I might do is get the standard
distribution and simply replace the few files that need changing and
tar it all back up again.

Have we decided on a naming scheme for all Perl ports yet?  I was using
"libwww-perl-5.41-1-port-MacOS.tgz" as a working name.

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

- -- 
Paul Schinder
schinder@pobox.com

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

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

Date: Wed, 3 Mar 1999 09:27:03 -0500
From: Chris Nandor <pudge@pobox.com>
Subject: [MacPerl-Modules] Fwd: More on binary builds and ports

I see Paul already got a copy of this.  No one responded to it (at least,
they did not copy me on it if they did).  :/

> Date: Tue, 23 Feb 1999 14:49:51 -0500
> To: modules@perl.org
> From: Chris Nandor <pudge@pobox.com>
> Subject: More on binary builds and ports
> Cc: schinder@pobox.com
> Bcc:
> X-Attachments:
>
> I was giving more thought to support for installing binaries and ports
> with CPAN.pm.
>
> I was thinking of a couple of things.  First, I like what was mentioned
> before about having something like:
>
>   Binary::GD::MacOS
>   Binary-GD-MacOS-1-1.18.tar.gz
>
> (The first digit is the build number.)
>
> Then I can do:
>
>   cpan> install GD
>
> If $CPAN::Config::binary_install is true, CPAN.pm would do a search for
> "Binary::${name}::$^O".  If found, CPAN.pm would ask:
>
>   A binary build of GD 1.18 for MacOS is available.  Do you want to get
> that
>   instead of the main distribution for GD 1.18? [n]
>
>
> Similarly, I was wondering about ports.  For example, MacPerl does not
> fully support LWP, and there is a port.  So how about:
>
>   Port::LWP::MacOS
>   Port-LWP-MacOS-1-5.41.tar.gz
>
>   cpan> install LWP
>
>   A port of LWP 5.41 for MacOS is available.  Do you want to get that
>   instead of the main distribution for LWP 5.42? [n]
>
> Of course, there is also the question of Bundles.  I imagine that it
> could work so that trying to install Bundle::LWP would, when
> encountering "LWP" in the Bundle file, would then fetch the port if the
> user responds affirmatively.
>
> Maybe there could be other configuration variables to set so that it
> installs without asking, too.  Or maybe not.
>
> The only thing left that I can think of offhand is that PAUSE would have
> to _not_ index the GD file in Binary-GD-MacOS, but only index
> Binary::GD::MacOS.
>
> Any problems, better solutions, things I didn't think of, etc.?  I'll
> think about starting work on this in the next few weeks if the consensus
> thinks it worthy.
>
> --
> 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 #4
***********************************


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