Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

Re^2: Mason on CentOS 6

by marmotking (Initiate)
on Dec 17, 2013 at 19:33 UTC ( #1067516=note: print w/replies, xml ) Need Help??


in reply to Re: Mason on CentOS 6
in thread Mason on CentOS 6

An excellent suggestion and excellent advise.

However, Log::Any isn't available through either the default CentOS repository or the RPMForge repository. Version 0.15 seems to be what's installed by default with the OS. I just took a step back and reinstalled the OS to a VM to start fresh. Having only installed the RPMForge repository, I get the same error with "yum install perl-HTML-Mason".

Perhaps HTML::Mason doesn't work on CentOS 6.4? I'm not sure how to force it to install without the dependency check on Log::Any. That's the next thing I'm looking into.

Replies are listed 'Best First'.
Re^3: Mason on CentOS 6
by marto (Bishop) on Dec 17, 2013 at 19:41 UTC

    Best to leave the system perl alone, if it gets messed up you can have a broken/unreliable system. perlbrew, makes this simple, even doing it manually is as little as 3 lines. Once you have your own perl install modules and their dependancies via cpan:

    cpan HTML::Mason

    Often versions of modules in OS repos are out of date.

      So, to summarize, it appears that HTML::Mason, as build in the RPMForge repository won't install with the system Perl. So, I may be able to sue Perlbrew to make a new Perl installation that I can use with HTML::Mason.

      This appears to mean that I'll also have to rebuild mod_perl using the new Perl installation that I create with Perlbrew. Not sure how to do that yet, but looking into it.

      I wonder if those people who work on the Mason project or the RPMForge project might want to look into fixing this, if it can be.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1067516]
help
Chatterbox?
[ELISHEVA]: Text::CSV_XS already can handle boms - see its detect_bom flag
[ELISHEVA]: but it seems that the DBD::CSV layer on top of it doesn't
[afoken]: Also: All other attributes that start with csv_ and are not described above will be passed to Text::CSV_XS (without the csv_ prefix).
[Discipulus]: what about a good 'ol SOPW?
[erix]: Giro d'Italia won by Dumoulin (peccato Nibali)
[ELISHEVA]: csv_detect_bom doesn't work either
[erix]: (SCNR)
[ELISHEVA]: I may have to resort to SOPW - but was hoping that this would be something simple
[erix]: I'd just remove the BOM, it is pretty simple
[ELISHEVA]: Simple yes. and I did consider that. but this isn't one off . An important data source that I don't control is generating bom prefixed utf8 files and I'd rather not have to be munging files every few months.

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (7)
As of 2017-05-28 20:31 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?