You don't really ever know where the "standard" Perl module directory is, do you?If you really asked me refering to the Perl installation shipped with a random distro, my answer was: I would never be sure until I did some test or lookup.
So, put the long story short, eventually, only this application in this particular distribution that sets @INC in such way. I believe this @INC hackery (borrowed from Tanktalus) won't affect other systems I don't need or don't have any interest to control.
I know it's against common practices, it's against my standard practices as well. I think the hard part with my OP is that it tries to force a frame, unusual frame of thinking. Now I can see it fails :-) That's why I said earlier that "Let's put aside for a while the debate around....". I kinda expected typical reactions I got so far, which I'm grateful for because it lets me know my sanity level (or, is it my insanity level?)
If you can make your system ten times as reliable by breaking convention, then do it and document the decision processI will, and thanks for reminding me. My OP is absolutely part of the docs :) The lengty was mostly to accommodate my intention to share what I went through during the process of the decision making. The part I apologized because I realized it might end up useless to anybody else.
Open source softwares? Share and enjoy. Make profit from them if you can. Yet, share and enjoy!
|Replies are listed 'Best First'.|
Re^3: Restricting @INC for specific application need
by mr_mischief (Monsignor) on Mar 06, 2008 at 17:27 UTC