Re^2: Shell style line-editing without benefit of CPAN modules

[SirBones]

Yes, yes. ++chromatic

To be a little more clear about the nature of my utility, it's not going to packaged as part of the final product. The machines themselves are controllers for much larger systems, and will go out to customers in this "plain vanilla" configuration for logistical, legal, and whatever reasons. My Perl code is only being used for engineering debug and bringup, and will be long gone before the machines go out. It's (usually) not the inclination of my boss to make my work more difficult; this is an unusual circumstance.

So in fairness, there are a lot of complex issues involved, and I didn't mean to over-simplify the Dilbert-nature of my workplace. Not in this case, anyway. ;-)

-Ken

[chromatic]

That's different, but I still think my point applies. The policy of not installing modules has a sane reason (we both assume), but in this case it has a cost tradeoff greater than a couple of hours. I don't see it as your job to decide how to proceed in such a case. I don't know what the right answer is for your business, but I do think it's worth bringing this up to your boss for advice.

This is one of those cases where something you didn't forsee in advance has the potential to change the scope of the work or the schedule. That happens. The best thing you can do is to identify it, be honest about the costs of all of the options, and let the person whose job it is to adjust the schedule or the scope do so.

[roboticus]

SirBones:

In that case, perhaps you could get someone to relent and let you install it in a *local* directory (like ~/perlib), and add that directory to your @INC for your debugging scripts. Then you can remove it all before delivery. That way, it needn't contaminate the normal /usr, /bin, /etc, etc. directories.

--roboticus