[Shipwright] Shipwright 2.4.31 and @INC

[David Good]

To wrap things up, I built and installed a brand-new 5.14.2 installation
as root (before I had built it as a user and installed it in my home
directory) and all my issues seem to have vanished.  I don't know what
about the system perl was causing the trouble, though.

If I build my shipyard and vessel as root, I see nothing out of the
ordinary, but if I install as a regular user it still installed
local::lib in my home directory and modifies my .bashrc.  I'm not crazy
about that side effect so I may just do my builds as root.


On 5/9/2012 5:15 PM, David Good wrote:
> OK, I reinstalled from scratch and made sure I installed the 'Developer
> Tools' and 'Developer Libraries' groups.  Everything goes smoothly until
> I try to import DBIx::Class.  I further narrowed it down to when
> importing DBD::SQLite.  I used '-l debug' when running the import and
> see in the log:
>
> DBI 1.57 is required to configure this module; please install it or
> upgrade your CPAN/CPANPLUS shell.
>
> So, I installed DBI in my system's perl via cpan. and that fixed that
> issue, but I'm still getting the same issue building CPAN::Meta.  I'm
> going to build a custom perl so I can eliminate the system perl as the
> problem (which seems the most likely at this point).
>
>
> On 5/9/2012 12:14 PM, David Good wrote:
>> I recall I had some initial weirdness with installing Shipwright via
>> CPAN (I discovered my VM didn't have gcc installed) so I'm going to try
>> a fresh reinstall and see if that helps.  If that doesn't work, I'll try
>> building my own perl to use for Shipwright.  I'll let you know what I
>> find...
>>
>> On 5/9/2012 11:39 AM, sunnavy wrote:
>>> Sorry, I missed your output of `shipwright -v`.
>>>
>>> You can omit the "as" directory I mentioned before, as it's created only after
>>> all dists are installed successfully.
>>>
>>> Still, I can't reproduce this, so I don't know what went wrong.
>>>
>>> Regards
>>> sunnavy
>>>
>>>