G'day ric00015,

A few tangential items:

• I use Tk with v5.18.1: it works fine; that's unrelated to your problem.
• The experimental warnings you're seeing were introduced in v5.18.0 - see "perl5180delta: The smartmatch family of features are now experimental" for an explanation and a way to disable them.
• Writing CORE when you mean CG::CORE2 is not helpful to us; doing this on the command line, in a configuration file or as part of your code, may result in a far worse outcome. Paying attention to detail is important! A simple search on CPAN can tell you whether you've chosen an unused namespace: compare search for 'CG::CORE2' (produces: "No matches") with search for 'CORE' (produces pages of matches).
• Embarking on a major upgrade (of anything) and just walking away for three days while it ran was a poor choice. Do you know what happened in that time? Do you have logs? Did the upgrade complete? Were there power outages or other events that may have caused problems? Your feedback mentions none of these things: we're left to make guesses.
• The issue of not performing backups has already been addressed. You said none were done prior to the upgrade; however, do you have no backups at all? Can you restore state as it existed, say, a few days ago?

With the scant information you've provided, my guess is that the environment used by your upgrade differed, in one or more respects, from the environment used for the initial installation. I don't know what the difference(s) might be. Non-exhaustive possibilities include:

• different user/group permissions (whether changed from the original or the result of running as another user)
• different method used for initial install and upgrade (could be different versions of the same program, e.g. /usr/bin/cpan vs. /usr/local/bin/cpan; different programs, e.g. cpan vs. cpanp; entirely different methods, e.g. cpan vs. a customised shell script with wget .../perl Makefile.PL/make/etc.)
• different environment variables controlling the process: there's a lot of these, see ExtUtils::MakeMaker to get an idea of the number and variety.

You say you installed a new version of Perl (5.18.1): did that overwrite the version used by Red Hat? is that a problem?

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.