MIME-Lite | the perl library MIME : :Lite | Email library
kandi X-RAY | MIME-Lite Summary
kandi X-RAY | MIME-Lite Summary
NAME MIME::Lite - low-calorie MIME generator. WAIT! MIME::Lite is not recommended by its current maintainer. There are a number of alternatives, like Email::MIME or MIME::Entity and Email::Sender, which you should probably use instead. MIME::Lite continues to accrue weird bug reports, and it is not receiving a large amount of refactoring due to the availability of better alternatives. Please consider using something else.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of MIME-Lite
MIME-Lite Key Features
MIME-Lite Examples and Code Snippets
Community Discussions
Trending Discussions on MIME-Lite
QUESTION
I'm working on a legacy product which uses the Docker perl:5.10-threaded
image and ran into an issue trying to debug things when I discovered there are two version of perl - one in /usr/local/bin/perl
and one in /usr/bin/perl
. In this particular image, they are actually different versions
/usr/local/bin/perl
-> 5.10.1/usr/bin/perl
-> 5.20.2
The issue it was causing is that each has a different @INC
path.
ANSWER
Answered 2019-Aug-05 at 16:09Perl is an essential part of many Linux distributions, and has to come pre-installed. The system perl that is used by the operating system is usually installed as /usr/bin/perl
. Modules for it are managed through the package manager (e.g. apt
) and not via cpan
/cpanm
. If you were to install modules for the system perl yourself, this might conflict with modules expected by the operating system. Worse, installing the wrong module version could break parts of the OS. Similarly, replacing the system perl is a bad idea. That's why those Docker images install the different perl alongside.
For your apps, you should avoid the system perl. If you want to install extra modules for use with the system perl, consider using local::lib. In some cases you might install dependencies such as C libraries or external tools via apt, but you wouldn't use apt-provided Perl modules.
Unless you are targeting a specific operating system, do not hardcode the #!/usr/bin/perl
shebang. Instead, prefer #!/usr/bin/env perl
so that the script will use the perl that is first in the PATH. Alternatively, use wrapper scripts to explicitly invoke the correct perl installation. For example:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install MIME-Lite
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page