symlink tutorial for Mercurial

[John Gateley]

Would someone be so kind as to give a brief tutorial on using
symlinks with Mercurial? I'm confused as to how they are supposed
to behave.

I have several perl projects, and several perl modules that are
shared between these projects. Currently, the perl modules are
saved in each project as a symlink:
proj1/
	file1.pl
	file2.pl
	sharedmodule.pm (symlink to perl/sharedmodule.pm)
proj2/
	file3.pl
	file4.pl
	sharedmodule.pm (symlink to perl/sharedmodule.pm)
perl/
	sharedmodule.pm

What is the best way to use Mercurial for this situation?
I'd expect two repositories, one in proj1 and one in proj2.
But I'd like it to do something "reasonable" with sharedmodule.pm

I don't want to make sharedmodule.pm it's own repository, and
create a dependency between proj1 and sharedmodule (a la
apt-get or dpkg), that's far too formal and cumbersome for
what I'm doing.

Thanks,

j
-- 
John Gateley <mercurial at jfoo.net>