Here's an untested example of what I mean:

package Foo;
use strict;
use warnings;

sub new {
  my $class = shift;
  $self = bless {@_}, $class;
  $self->init_logging();
}

sub init_logging {
  my $self = shift;
  return if exists $self->{LOGGER};
  eval {
    require SomeLogger;
    $self->{LOGGER} = SomeLogger->new();
  };
}

sub debug {
  my $self = shift;
  return unless exists $self->{LOGGER};
  $self->{LOGGER}->debug(@_);
}
[download]

my $logger = SomeOtherLogger->new(log_level => 'debug');
my $foo = Foo->new(LOGGER => $logger);
[download]

use Scalar::Util qw( blessed );
sub debug {
  my $self = shift;
  return unless exists $self->{LOGGER};
  return unless blessed $self->{LOGGER};
  return unless $self->{LOGGER}->can('debug');
  $self->{LOGGER}->debug(@_);
}
[download]

Update - switched to require within the eval, per chromatic's suggestion

Do you mean instead:

require SomeLogger;

... in the eval block? I'm not sure whether you intended a conditional load.

Aye, that was my intent.

eval {
  require SomeLogger;
  $self->{LOGGER} = SomeLogger->new();
};
[download]

You shouldn't force them one way or the other. Make the dependency optional; detect the presence of Log4perl at run time; use if present.

Personally, I'd isolate the logging bits behind a generic interface, that is, a wrapper; then I'd make another wrapper for a different logging module. If it turns out to be easy, you could do several. Detect the presence of any of them at run time (in some kind of priority order), and use one if found. I've done something like this for XML parsing modules.