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 thing that would be reassuring to me is the ability to 
find/view/remove any and all files installed by Alien::XXX.

Just some things I've been bitten by with the original Alien approach...

Cheers,
Chris


On 5/31/2015 16:27, Zakariyya Mughal wrote:
> 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 
>> afterwards, PDL 2.010 which depends on PDL::Core 2.010, but still has all 
>> the other stuff still in. The reason is that a separated-out PDL::Core is 
>> the “minimum viable product” (in this case, minimal change to the existing 
>> distro), on which the next part (below) depends.
>>
>> Obviously, we also need to make individual CPAN releases of all the 
>> currently-incorporated non-core modules. Each will need:
>>    1.. its own repo – I strongly suggest putting them on Github, set up with 
>> all the goodies that Zaki made happen for PDL, with Travis and the IRC 
>> notifications;
> Yes, thanks to Christian Walde' (Mithaldu) for setting up the mirroring
> and recently adding all the current SF repos to GitHub as well
> (pdl-linearalgebra, pdl-io-hdf5, etc.). See <https://github.com/PDLPorters>.
>
>>    2.. the history moved over from the current PDL repo into that repo (I 
>> can do that once it’s set up, it’s straightforward enough);
> I seem to recall this was also done with Inline and Inline::C when they
> were split about a year ago?
>
>>    3.. sufficient build-system munging to make them work as a standalone 
>> distro (I can take care of that, it’s easy with EUMM)
>>    4.. someone to “own” it (defaulting to Chris, but if someone else is 
>> motivated to take it on, that surely will make Chris’s life easier)
>>    5.. an actual CPAN release by whomever is the “owner”
>> If everyone is happy with this as a general concept, I can go ahead and make 
>> a list of all the individual new distros, and start executing points 2 & 3 
>> for each of them. I’ll be asking Zaki for his expertise on point 1 for each. 
>> Zaki, will you feel like taking on release ownership of some of the distros?
> Sure, I'll try my hand at a couple and then take what I learned from
> those to apply them to the others. I was thinking that starting with
> PDL::IO::GD might work nicely since that might involve also creating an
> Alien::GD.
>
> Cheers,
> - Zaki Mughal
>
>> The final step when this is all sorted, is to release “PDL” as just a small 
>> empty distro that has dependencies on PDL::Core plus all the split-out 
>> modules, for those who want to get the same as there is now, with the same 
>> CPAN command.
>>
>> Best regards,
>> Ed
>>
>> From: Chris Marshall
>> Sent: Friday, May 29, 2015 10:53 PM
>> To: pdl-devel@lists.sourceforge.net
>> Subject: [Pdl-devel] PAUSE indexer is happy with PDL-2.009
>>
>> Thanks for all the help and great work!
>>
>>
>> --Chris
>>

------------------------------------------------------------------------------
_______________________________________________
pdl-devel mailing list
pdl-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pdl-devel

Reply via email to