On Sun, May 31, 2015 at 3:42 PM Zakariyya Mughal
wrote:
> On 2015-05-31 at 16:35:33 -0400, Chris Marshall wrote:
> > One problem I've had with Alien installs is control of the install
> process.
> >
> > In most cases, as a PDL user I *don't* want unknown
> > build-test-install processes to take p
Zaki,
As you'll see from
https://github.com/ingydotnet/inline-c-pm/commits/master?page=5 , Inline::C
didn't have its history copied over. You have to look at Inline's history
for previous Inline::C history. I think that's a shame, so I'll be making
the small extra effort.
If you like, I can s
On 2015-05-31 at 16:35:33 -0400, Chris Marshall wrote:
> One problem I've had with Alien installs is control of the install process.
>
> In most cases, as a PDL user I *don't* want unknown
> build-test-install processes to take place without my concurrence.
> I would far prefer a LibDetect::XXX fi
One problem I've had with Alien installs is control of the install process.
In most cases, as a PDL user I *don't* want unknown build-test-install
processes to take place without my concurrence. I would far prefer a
LibDetect::XXX first with an option of Alien::XXX install after that.
Another
On 2015-05-30 at 14:42:46 +0100, Ed wrote:
> Chris,
>
> Great work!
>
> Now to press towards “splitting the iceberg”. I have a branch already that
> will make a PDL::Core release 2.010, which consists of the current Basic/ and
> Doc/. I am very keen to release PDL::Core 2.010, and then straight
This release checks some clean up for PDL-2.008, PDL-2.009 regarding
moving PDL::Graphics::PLplot to its own CPAN distribution. If it checks
out, it will become PDL-2.010. Please test and report!
Thanks,
Chris and the PDL Developers
Release Notes for PDL 2.009_01 -
