Best way to include developer version of a module

--===============0845147130==
Content-Type: multipart/alternative; boundary=000325575aeafb762a048f44be84

--000325575aeafb762a048f44be84
Content-Type: text/plain; charset=ISO-8859-1

The Mail::Sendmail module included in the ppm repositories, and installed
using either ppm or cpan is version 0.79 (dated 06 Feb 2003). There is a
"developer" release 0.79_16 (dated 08 Jul 2006) that has significant
enhancements, not least SMTP AUTH support.

I could not find an elegant way to force cpan to pick up that version, and
have been just downloading the tar and overwriting the Sendmail.pm file.

What is the recommended way of handling this issue?

--
Tim Bolshaw

--000325575aeafb762a048f44be84
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The Mail::Sendmail module included in the ppm repositories, and installed u=
sing either ppm or cpan is version 0.79 (dated 06 Feb 2003). =A0There is a =
"developer" release 0.79_16 (dated 08 Jul 2006) that has signific=
ant enhancements, not least SMTP AUTH support.

Re: Best way to include developer version of a module

On 9/2/2010 4:02 AM, Tim Bolshaw wrote:
> The Mail::Sendmail module included in the ppm repositories, and installed using either ppm or cpan is version 0.79 (dated 06 Feb 2003). There is a "developer" release 0.79_16 (dated 08 Jul 2006) that has significant enhancements, not least SMTP AUTH support.
>
> I could not find an elegant way to force cpan to pick up that version, and have been just downloading the tar and overwriting the Sendmail.pm file.
>
> What is the recommended way of handling this issue?

What does Mail::Sendmail have that MIME::Lite doesn't have ?

In other words - it may be the wrong package for the job.
At least make a comparison for the features you need and
see if it's even worth the effort.
_______________________________________________
ActivePerl mailing list
ActivePerl@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

RE: Best way to include developer version of a module

This is a multipart message in MIME format.

--===============0720056704==
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_01C9_01CB4F55.B81F8900"
Content-Language: en-us

This is a multipart message in MIME format.

------=_NextPart_000_01C9_01CB4F55.B81F8900
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

You need to specify the authors CPAN directory when you want to install =
a developer version of a module because they are not
included in the normal module index. So the =93elegant=94 command to =
install that module using the CPAN shell is:

=20

cpan M/MI/MIVKOVIC/Mail-Sendmail-0.79_16.tar.gz

=20

Cheers,

-Jan

=20

From: activeperl-bounces@listserv.ActiveState.com =
[mailto:activeperl-bounces@listserv.ActiveState.com] On Behalf Of Tim =
Bolshaw
Sent: Thursday, September 02, 2010 4:02 AM
To: activeperl@listserv.activestate.com
Subject: Best way to include developer version of a module

=20

The Mail::Sendmail module included in the ppm repositories, and =
installed using either ppm or cpan is version 0.79 (dated 06 Feb
2003). There is a "developer" release 0.79_16 (dated 08 Jul 2006) that =
has significant enhancements, not least SMTP AUTH support.

=20

I could not find an elegant way to force cpan to pick up that version, =
and have been just downloading the tar and overwriting the
Sendmail.pm file.

=20

What is the recommended way of handling this issue?

--=20
Tim Bolshaw


------=_NextPart_000_01C9_01CB4F55.B81F8900
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"> http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1252"> 14 (filtered medium)"> vlink=3Dpurple>