Well, according to his code, importer is never called since he explicitly uses empty lists after use ...

> > use gitadm_shell_commands();

importer is never called

It depends on how far the modules follow the common practices (look at their names). Try:

script.pl:

#!/usr/bin/perl
use warnings;
use strict;

use Ugly ();

puke('Where does it come from?');
[download]

Ugly.pm:

package Ugly;

use warnings;
use strict;

my $package = (caller)[0];

sub puke {
    warn @_;
}

{   no strict 'refs';
    *{$package . '::puke'} = \&puke;
}

__PACKAGE__
[download]

لսႽ† ᥲᥒ⚪⟊Ⴙᘓᖇ Ꮅᘓᖇ⎱ Ⴙᥲ𝇋ƙᘓᖇ

Sure, I deliberately decided to ignore those dirty possibility. =)

There are to many ways to pollute the namespace to be listed, at the end the OP should clarify how his code works.

From the sparse information provided, we can't tell much.

And he is redefining a sub with the same name, so I suppose nothing should be imported.

Cheers Rolf

( addicted to the Perl Programming Language)

Could you possibly forget to define a package gitadm_shell_commands in your gitadm_shell_commands.pm file?

Try checking symbol table for your sub in case it's left defined somewhere else:

{
 no strict 'subs';
 sub print_subs {
  for (keys %{$_[0]}) {
   next if $_ eq $_[0];
   print "$_[0]$_\n" if defined *{$_}{CODE};
   print_subs($_[0].$_) if /::$/; # dirty hack
  }
 }
 print_subs("main::");
}
[download]