I'm aware of following options:

• to the system via CPAN shell (own code in special checkout folder, own distributions by hand)
• CPAN::Mini::Inject - creating DarkPAN, then using CPAN shell
• to the system via OS packages (packages of non-public stuff needs to be created)
• local::lib
• whole Perl to a special dedicated folder (with help of perlbrew)
• having the whole codebase in VC repository and doing checkouts or rsync
• PAR/Shipwright to create an executable that contains "everything"
• one NFS share for lib

Any other clever option? Any complete solution? Any successful stories how to manage huge codebases on a lot of servers?

Let's explain why I'm asking - I'm collecting the real world solution for my talk on YAPC::EU::2011. I don't want to miss some important or clever solutions.

---

---

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.