blocks|key|654318|text|正确的方法是告诉他们“不要那样做！”我希望他们不会期望移动一个exe文件并让程序继续工作。这也没什么不同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|654319|这就是说，有几种选择。一种是用包装器(例如pl2bat)替换脚本，它知道实际脚本的完整路径。另一种方法是使用PAR，但这需要安装PAR和/或parl+(来自PAR::Packer)。|offset|length|654320|entityMap|0|LINK|mutability|MUTABLE|url|http://search.cpan.org/perldoc?PAR^0|0|1I|3|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

The right way is to tell them "Don't do that!" I would hope that they wouldn't expect to move an exe file and have the program continue to work. This is no different.

That said, there are a couple of alternatives. One is replacing the script with a wrapper (e.g. pl2bat) that knows the full path to the real script. Another is to use <a href="http://search.cpan.org/perldoc?PAR" rel="noreferrer">PAR</a>, but that would require PAR and/or parl (from PAR::Packer) to be installed.

blocks|key|4436713|text|如果您为客户端准备的脚本需要“自定义”模块，则只需将您的模块打包，就像您试图将它们上传到cpan一样。然后将包提供给客户端，客户端可以使用cpan实用程序安装脚本和模块。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4436714|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If a script that your prepared for a client needs "custom" modules, simply pack your modules as if you were trying to upload them to cpan. Then give the package to the client and he can use the cpan utility to install the script and the modules.

blocks|key|2969084|text|随脚本一起分发安装程序。安装程序需要以root权限运行，它会将定制模块放入标准系统位置(/usr/local/lib/perl5/site_perl或其他位置)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2969085|我还没有尝试过，但是Module::Install在这方面看起来很有帮助。它被描述为：|2969086|2969087|独立、可扩展的Perl模块安装程序|blockquote|2969088|2969089|entityMap|0|LINK|mutability|MUTABLE|url|http://search.cpan.org/dist/Module-Install/lib/Module/Install.pod^0|0|B|0|A|F|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@$9|Y|A|Z|1|10]]|E|$]]|$1|H|3|-4|5|6|7|11|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|12|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|13|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

Distribute an installer along with the script. The installer will need to be run with root privileges and it will put the custom modules into the standard system location (/usr/local/lib/perl5/site_perl or whatever).

I've not tried this, but <a href="http://search.cpan.org/dist/Module-Install/lib/Module/Install.pod" rel="nofollow noreferrer">Module::Install</a> looks helpful in this regard. It's described as a:

<blockquote>
 Standalone, extensible Perl module installer
</blockquote>

blocks|key|654405|text|作为“把你的所有模块放在一个地方，让你的应用程序意识到这一点”的变体，甚至可以跨多台计算机和网络工作，也许你应该检查一下PAR::Repository和各自的PAR::Repository::Client。您只需提供一个二进制客户端可执行文件，它就可以(通过文件系统或https)连接到存储库，并执行用户请求的存储库提供的任意数量的程序(使用任意一组模块)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|654406|如果有许多用户，这对维护也有好处:只需更新存储库提供的软件，用户在下次启动程序时就会开始使用更新后的代码。|654407|entityMap|0|LINK|mutability|MUTABLE|url|http://search.cpan.org/dist/PAR-Repository|1|http://search.cpan.org/dist/PAR-Repository-Client^0|1O|F|0|27|N|1|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

As a variant of the "put your modules all in one place and make your applications aware of it" that will even work across multiple computers and networks, maybe you should check out <a href="http://search.cpan.org/dist/PAR-Repository" rel="nofollow noreferrer">PAR::Repository</a> and respectively <a href="http://search.cpan.org/dist/PAR-Repository-Client" rel="nofollow noreferrer">PAR::Repository::Client</a>. You'd just provide a single binary client executable that connects to the repository (via file system or https) and executes any of the arbitrary number of programs (using an arbitrary set of modules) provided by the repository that the user asks for.

If there are many users, this also has a benefit for maintenance: Simply update the software provided by the repository and the users will start using the updated code for their system when they next start the programs.

blocks|key|927781|text|如果你能使用一个NeXTSTEP+style+application捆绑包，那就太好了。由于您可能不是在为使用包的平台进行开发，所以您只能凑合着使用。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|927782|将所有支持文件放在已知位置，并将可执行文件指向这些文件以访问设置和库。最简单的方法是使用一个简单的安装程序。|927783|例如，使用名为foo的应用程序，将所有需要的文件放在/opt/xlyd_apps/foo中，将库放在/opt/xlyd_apps/foo/lib中，将配置放在/opt/xlyd_apps/foo/etc中，依此类推。将可执行文件放入/opt/xlyd_apps/foo/bin。|style|CODE|927784|重要的是要确保可执行文件知道在/opt/xlyd_apps/foo中查找它的所有优点，因此，如果客户/客户将foo脚本移动到新位置，安装仍然有效。|927785|因此，虽然您不能使整个东西自包含和可重定位，但您已经使实际的调用脚本可重定位。|927786|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Application_Bundle^0|8|Q|0|0|0|7|3|Q|I|1E|M|27|M|38|M|0|F|I|1I|3|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|10|8|@$A|11|B|12|H|I]|$A|13|B|14|H|I]|$A|15|B|16|H|I]|$A|17|B|18|H|I]|$A|19|B|1A|H|I]]|9|@]|C|$]]|$1|J|3|K|5|6|7|1B|8|@$A|1C|B|1D|H|I]|$A|1E|B|1F|H|I]]|9|@]|C|$]]|$1|L|3|M|5|6|7|1G|8|@]|9|@]|C|$]]|$1|N|3|-4|5|6|7|1H|8|@]|9|@]|C|$]]]|O|$P|$5|Q|R|S|C|$T|U]]]]

It would be really nice if you could just use a <a href="http://en.wikipedia.org/wiki/Application_Bundle" rel="nofollow noreferrer">NeXTSTEP style application</a> bundle. Since you probably aren't developing for a platform that uses bundles, you'll have to make do.

Put all support files in a known location, and point your executable at those files for access to settings and libraries. The easiest way to do this is with a simple installer.

For example, with an app called <code>foo</code>, put all your required files in <code>/opt/xlyd_apps/foo</code>, libraries in <code>/opt/xlyd_apps/foo/lib</code>, configuration in<code>/opt/xlyd_apps/foo/etc</code>, and so on. Put the executable in <code>/opt/xlyd_apps/foo/bin</code>.

The important thing is to make sure the executable knows to look in <code>/opt/xlyd_apps/foo</code> for all its goodies, so if the customer/client move the <code>foo</code> script to a new location the install still works.

So, while you can't make the whole thing self contained and relocatable, you have made the actual calling script relocatable.

blocks|key|654441|text|实际上，我已经想出了我自己的解决方案，我很好奇它会受到什么样的欢迎。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|654442|我已经编写了一个脚本来读取perl脚本并查找"use/require“语句。一旦找到它们，它就会检查该模块是否属于标准库(查看/perl5/\d%2B.\d%2B\d.%2B/的模块路径)，然后根据使用情况以两种不同的方式重写use/require行。|654443|如果找到需要的：|offset|length|style|BOLD|654444|{
++++...+inline+the+entire+module+here...
}|code-block|syntax|javascript|654445|如果找到使用的：|654446|BEGIN+{
++++...+inline+the+entire+module+here...
}|654447|如果use有imports，请立即在上面输入：|654448|BEGIN+{+import+Module+...imports+seen...+}|654449|我知道这个不能对使用XS的模块进行操作，但是我对此很满意。大多数情况下，我只需要支持纯perl模块。|654450|entityMap^0|0|0|7|1|0|0|0|6|7|1|0|0|0|N|0|0|0|1E|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|12|8|@$F|13|G|14|H|I]]|9|@]|A|$]]|$1|J|3|K|5|L|7|15|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|16|8|@$F|17|G|18|H|I]|$F|19|G|1A|H|I]]|9|@]|A|$]]|$1|Q|3|R|5|L|7|1B|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|6|7|1C|8|@$F|1D|G|1E|H|I]]|9|@]|A|$]]|$1|U|3|V|5|L|7|1F|8|@]|9|@]|A|$M|N]]|$1|W|3|X|5|6|7|1G|8|@$F|1H|G|1I|H|I]]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|Z|$]]

I've actually come up with my own solution, and I'm kind of curious what kind of reception it will have.

I've written a script that reads a perl script and looks for "use/require" statements. Upon finding them it checks if the module is part of the standard library (looks at module path for /perl5/\d+.\d+[\d.]+/) and then rewrites the use/require line in two different ways depending on usage.

If require is found:

<pre><code>{
 ... inline the entire module here...
}
</code></pre>

If use is found:

<pre><code>BEGIN {
 ... inline the entire module here...
}
</code></pre>

If use has imports, immediately follow above with:

<pre><code>BEGIN { import Module ...imports seen... }
</code></pre>

I understand this doesn't work with modules that use XS, but I was fine with this. Mostly I need to support only pure perl modules.

How can someone distribute native (non-"compiled/perl2exe/...") Perl scripts without forcing users to be aware of the custom (non-CPAN) modules that the scripts needs in order to run?

The problem is users will inevitably copy the script somewhere else on the system and take the script out of its native environment and then it can no longer find the modules it needs to run.

I've sometimes settled with just copying the module into the actual script, but I'd prefer a cleaner solution.

Update: I better clarify. I distribute a bunch of scripts which happen to use similar modules in the backend. The users understand how to run Perl scripts, but rather than relying on telling them "no don't move the script" I'd prefer to simply allow them to move the files. The path of least resistence.

How to distribute native perl scripts without custom module overhead?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

如何分发本机(非“已编译/perl2exe/...”)Perl脚本，而不强制用户知道脚本运行所需的自定义(非CPAN)模块？问题是，用户将不可避免地将脚本复制到系统上的其他地方，并将脚本从其本机环境中取出，然后它将无法再找到它需要运行的模块。我有时只是将模块复制到实际的脚本中，但我更喜欢更干净的解决方案。更新:我最好澄清一下。我分发了一堆脚本，这些脚本恰好在后端使用了类似的模块。用户知道如何运行P

问如何在没有自定义模块开销的情况下分发原生perl脚本？
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在没有自定义模块开销的情况下分发原生perl脚本？EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在没有自定义模块开销的情况下分发原生perl脚本？
EN