[publican-list] Publican 2.3 - not using files in Common_Content

[Norman Dunbar]

Morning Jeff,

On 21/08/13 06:07, Jeff Fearn wrote:

> FWIW the CPAN install is very rare, so you are a bit of a guinea pig
> here ... thanks :)
>
>> $ sudo ./Build install
>>
> Fixed for next commit.

Thanks!


> I'd really need a full log of the entire process to have a real crack at
> solving this. It's possible there is something funky going on with the
> Config.

I've created a bug for this, as requested, and there's a full log on 
that of the build process from creating the book to building it. I 
turned debug on in the config to get as much output as possible, but I 
doubt it will be helpful. Is there some way to get more that what is 
displayed on screen for a build? I looked around but couldn't find anything.

> Publican uses Module::Build::ConfigData to track where things are
> installed, it's possible there is some memory state hanging around
> between install and building a book.
>
> $ perl -e 'use Publican::ConfigData; print
> Publican::ConfigData->config('datadir'), "\n";'
> /usr/share/publican

Running that command gives:

/home/norman/Publican/Publican-v3.2.0/blib/datadir


> Can you open a bug with a link to the section? The doc is way out of
> date, common_config & common_content are command line options and won't
> get used from the publican.cfg.

https://bugzilla.redhat.com/show_bug.cgi?id=999427


> Unless you override them on the command line:
>
> common_config  = Publican::ConfigData->config('datadir')
> common_content = Publican::ConfigData->config('datadir') .
> '/Common_Content'

That seems to be wroking but using my locally installed files rather 
than the ones that "sudo ./Build install" created in /usr/share/publican 
- none of which existed prior to the command to install Publican being run.


Cheers,
Norm.

-- 
Norman Dunbar
Dunbar IT Consultants Ltd

Registered address:
27a Lidget Hill
Pudsey
West Yorkshire
United Kingdom
LS28 7LG

Company Number: 05132767