in reply to Re^2: Set include path
in thread Set include path
The first: use lib '/lib' will attempt to find your library file in the root of the current drive. If you mean that it should look in the lib directory under the current directory, then use lib 'lib' would be appropriate, although potentially risky 1.
moritz has addressed the usage issue with your other attempt.
1 - Given that any attacker could probably copy your script anyway, I am having a hard time adding any additional risk by a user being able to replace your library with one that they 'own', therefore the use of 'potentially'.