blocks|key|700540|text|首先，这里可能是最相关的文档：Debian策略手册:包维护人员描述和安装过程。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|700541|第二，在编写或处理维护脚本时，最重要的事情是必须记住:它们必须是幂等的。假设脚本将连续运行许多次，并确保这样的脚本不会中断。|style|BOLD|700542|直接回答你的问题，|700543|使用DEBIAN构建时，将其放入dpkg-deb目录是正确的。如果您使用Debhelper进行更安全或更方便的构建设置，则可以将postinst放在debian/$packagename.postinst中。|ordered-list-item|CODE|700544|postinst脚本可以在许多不同的情况下调用。你能在很多(大多数？)中找到的“案例”语句。邮递员的意思是检查是哪一种情况。一般来说，在所有可能的情况下采取大多数事后行动是有意义的，这就是为什么它们被组合在一个脚本中的原因。但有时区分比较好。我将在#4下面解释不同的场景。|700545|是。如果存在，成功安装deb包(无论是通过dpkg+-i、apt-get+install还是其他方式)必须涉及成功运行它的前脚本和后期脚本。可以在不运行任何维护脚本的情况下“解压”deb，但这不被认为是“安装”。|700546|这些"action“名称对应于可以运行postinst的不同情况。|700547|-+_configure_:+A+package+is+being+installed+or+upgraded.+If+the+package+wasn't+installed+before,+`$2`+will+be+empty.+Otherwise+`$2`+will+contain+the+old+version+number+of+the+package;+the+version+from+which+you+are+upgrading.
-+_abort-upgrade_:+An+upgrade+operation+was+aborted.+As+an+example,+I+have+version+V1+of+mypkg+installed,+and+I+try+to+upgrade+it+to+V2.+But+the+preinst+or+postinst+of+V1+fail+to+run+successfully,+or+there+is+a+file+conflict.+dpkg+stops+trying+to+install+V2,+and+re-runs+the+postinst+from+V1+(with+the+"`abort-upgrade`"+action)+in+case+any+state+needs+to+be+restored.
-+_abort-remove_:+A+remove+operation+was+aborted.+For+example,+if+I+ran+"dpkg+-P+mypkg",+but+mypkg's+prerm+script+failed+to+run,+or+something+else+happened+that+made+dpkg+think+it+could+not+safly+uninstall+mypkg.+So+it+runs+mypkg's+postinst+again+(with+the+"`abort-remove`"+action)+in+case+any+state+needs+to+be+restored.
-+_abort-deconfigure_:+As+you+might+guess,+a+deconfigure+operation+was+aborted.+"deconfiguring"+is+sort+of+a+half-removal+action+used+when+a+package+being+installed+conflicts+with+others+already+installed.+To+make+the+explanation+short,+if+the+`abort-deconfigure`+action+is+being+run,+the+postinst+is+expected+to+restore+any+state+that+might+have+been+undone+by+the+`prerm`+script+with+the+`deconfigure`+action.|code-block|syntax|javascript|700548|要获得更多的细节，请参见https://people.debian.org/~srivasta/MaintainerScripts.html的伟大图表和解释。|700549|“更新-替代”命令更新Debian+"alternatives“系统中的条目。请看手册页。在这个特定的例子中，命令告诉Debian+"/usr/bin/fakeroot-ng“是fakeroot命令的另一种选择。根据这个选项的优先级和其他注册替代的优先级，以及用户的偏好，现在可以在某人运行"fakeroot“时调用fakeroot。|700550|entityMap|0|LINK|mutability|MUTABLE|url|https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html|1|https://people.debian.org/~srivasta/MaintainerScripts.html|2|http://manpages.debian.org/cgi-bin/man.cgi?query=update-alternatives&apropos=0&sektion=0&manpath=Debian%2B7.0%2Bwheezy&format=html&locale=en^0|F|N|0|0|F|7|T|X|0|0|9|0|0|2W|2|6|G|8|22|S|0|0|3S|0|0|2Y|L|7|T|F|0|0|X|0|0|0|27|C|1M|1|0|0|4N|1V|K|2H|8|42|8|4E|8|13|6|2|0^^$0|@$1|2|3|4|5|6|7|1E|8|@]|9|@$A|1F|B|1G|1|1H]]|C|$]]|$1|D|3|E|5|6|7|1I|8|@$A|1J|B|1K|F|G]|$A|1L|B|1M|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|1N|8|@$A|1O|B|1P|F|G]]|9|@]|C|$]]|$1|J|3|K|5|L|7|1Q|8|@$A|1R|B|1S|F|G]|$A|1T|B|1U|F|M]|$A|1V|B|1W|F|M]|$A|1X|B|1Y|F|M]]|9|@]|C|$]]|$1|N|3|O|5|L|7|1Z|8|@$A|20|B|21|F|G]]|9|@]|C|$]]|$1|P|3|Q|5|L|7|22|8|@$A|23|B|24|F|G]|$A|25|B|26|F|M]|$A|27|B|28|F|M]]|9|@]|C|$]]|$1|R|3|S|5|L|7|29|8|@$A|2A|B|2B|F|G]]|9|@]|C|$]]|$1|T|3|U|5|V|7|2C|8|@]|9|@]|C|$W|X]]|$1|Y|3|Z|5|6|7|2D|8|@$A|2E|B|2F|F|G]]|9|@$A|2G|B|2H|1|2I]]|C|$]]|$1|10|3|11|5|L|7|2J|8|@$A|2K|B|2L|F|G]|$A|2M|B|2N|F|M]|$A|2O|B|2P|F|M]|$A|2Q|B|2R|F|M]|$A|2S|B|2T|F|M]]|9|@$A|2U|B|2V|1|2W]]|C|$]]|$1|12|3|-4|5|6|7|2X|8|@]|9|@]|C|$]]]|13|$14|$5|15|16|17|C|$18|19]]|1A|$5|15|16|17|C|$18|1B]]|1C|$5|15|16|17|C|$18|1D]]]]

First, here is possibly the most relevant documentation: <a href="https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html" rel="nofollow">Debian Policy Manual: Package Maintainer Scripts and Installation Procedure</a>.

Second, the very most important thing to remember when writing or dealing with maintainer scripts is that they must be idempotent. Assume the script will be run many times in succession, and make sure things still won't break if so.

To answer your questions directly,

<ol>
<li>Putting it in the <code>DEBIAN</code> directory is correct, when building with <code>dpkg-deb</code>. If you were instead using Debhelper for a safer or more convenient build setup, you might put the postinst in <code>debian/$packagename.postinst</code>.</li>
<li>The postinst script can be called in a number of different situations. The "case" statement you can find in many (most?) postinsts is meant to check which situation it is. Generally speaking, it makes sense to take most postinst actions in all of the possible situations, and that's why they are grouped together in one script. But sometimes it is better to differentiate. I'll explain the different scenarios under #4.</li>
<li>Yes. A successful installation of a deb package (whether by <code>dpkg -i</code>, <code>apt-get install</code>, or whatever) must involve a successful run of its preinst and postinst scripts, if present. It is possible to "unpack" a deb without running any maintainer scripts, but that is not considered "installing".</li>
<li>These "action" names correspond to the different situations in which a postinst can be run.

<ul>
<li>configure: A package is being installed or upgraded. If the package wasn't installed before, <code>$2</code> will be empty. Otherwise <code>$2</code> will contain the old version number of the package; the version from which you are upgrading.</li>
<li>abort-upgrade: An upgrade operation was aborted. As an example, I have version V1 of mypkg installed, and I try to upgrade it to V2. But the preinst or postinst of V1 fail to run successfully, or there is a file conflict. dpkg stops trying to install V2, and re-runs the postinst from V1 (with the "<code>abort-upgrade</code>" action) in case any state needs to be restored.</li>
<li>abort-remove: A remove operation was aborted. For example, if I ran "dpkg -P mypkg", but mypkg's prerm script failed to run, or something else happened that made dpkg think it could not safly uninstall mypkg. So it runs mypkg's postinst again (with the "<code>abort-remove</code>" action) in case any state needs to be restored.</li>
<li>abort-deconfigure: As you might guess, a deconfigure operation was aborted. "deconfiguring" is sort of a half-removal action used when a package being installed conflicts with others already installed. To make the explanation short, if the <code>abort-deconfigure</code> action is being run, the postinst is expected to restore any state that might have been undone by the <code>prerm</code> script with the <code>deconfigure</code> action.</li>
</ul>

For lots of additional nitty-gritty details, see the great charts and explanations at <a href="https://people.debian.org/~srivasta/MaintainerScripts.html" rel="nofollow">https://people.debian.org/~srivasta/MaintainerScripts.html</a> .</li>
<li>The "update-alternatives" command updates entries in the Debian "alternatives" system. <a href="http://manpages.debian.org/cgi-bin/man.cgi?query=update-alternatives&amp;apropos=0&amp;sektion=0&amp;manpath=Debian+7.0+wheezy&amp;format=html&amp;locale=en" rel="nofollow">See the man page.</a> In this specific case, the command is telling Debian that "<code>/usr/bin/fakeroot-ng</code>" is an alternative for the <code>fakeroot</code> command. Depending on the priority of this alternative and the priority of other registered alternatives, and the preference of the user, <code>fakeroot-ng</code> might now be invoked when someone runs "<code>fakeroot</code>".</li>
</ol>

blocks|key|1721711|text|只要想想这句话：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1721712|echo+/usr/local/lib+>+/etc/ld.so.conf+&&+ldconfig|code-block|syntax|javascript|1721713|根据Debian政策，你不应该修改ld.so.conf|offset|length|1721714|一个简单的选择是这样做：|1721715|后脚本中的+:|style|BOLD|1721716|/usr/local/lib+>+/etc/ld.so.conf.d/EXAMPLE.conf+&&+ldconfig|1721717|和postrm脚本中的|1721718|rm+/etc/ld.so.conf.d/EXAMPLE.conf+&&+ldconfig|1721719|entityMap|0|LINK|mutability|MUTABLE|url|https://lintian.debian.org/tags/maintainer-script-should-not-modify-ld-so-conf.html^0|0|0|B|G|0|0|0|5|2|0|0|0|B|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|16|8|@]|9|@$I|17|J|18|1|19]]|A|$]]|$1|K|3|L|5|6|7|1A|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1B|8|@$I|1C|J|1D|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1E|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|1F|8|@$I|1G|J|1H|O|P]]|9|@]|A|$]]|$1|U|3|V|5|D|7|1I|8|@]|9|@]|A|$E|F]]|$1|W|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]]]

Just one think about this line :

<pre><code>echo /usr/local/lib &gt; /etc/ld.so.conf &amp;&amp; ldconfig
</code></pre>

According the Debian Policy, <a href="https://lintian.debian.org/tags/maintainer-script-should-not-modify-ld-so-conf.html" rel="nofollow">you shouldn't modify ld.so.conf</a>

A simple alternative is to do something like that :

In your postinst script :

<pre><code>/usr/local/lib &gt; /etc/ld.so.conf.d/EXAMPLE.conf &amp;&amp; ldconfig
</code></pre>

and in your postrm script :

<pre><code>rm /etc/ld.so.conf.d/EXAMPLE.conf &amp;&amp; ldconfig
</code></pre>

Good afternoon,

I was able to build my project into a deb package using:

<pre><code>fakeroot dpkg-deb --build mypackage
</code></pre>

Next, I can install the package using

<pre><code>dpkg -i mypackage.deb
</code></pre>

Everything is installed and copied correctly when I do this, however I would like to run a few bash commands after the package is installed.

I understand this needs to be done using the postinst file in the mypackage/DEBIAN directory

I have seen a few examples of this script online, but no clear explanation of how to write one and how to include it in the build.

<ol>
<li>How do I make sure fakeroot dpkg-deb includes this script, is placing it into DEBIAN directory enough?</li>
<li>There is a case structure in the postinst script, what is this for, and where do I place the bash commands to execute in that script</li>
<li>If I install the package with dpkg - i mypackage.deb is this enough to run that script?</li>
</ol>

An example script I would like to make is shown below. 

<ol start="4">
<li>What do "configure, abort-upgrade, abort-remove, and abort-deconfigure" stand for. </li>
<li>What does the "update-alternatives" line do.</li>
</ol>

Thank you for your help,

postinst file below.

<pre><code>#!/bin/sh

set -e

case "$1" in
 configure)
 # EXECUTE MY BASH COMMAND
 echo /usr/local/lib &gt; /etc/ld.so.conf &amp;&amp; ldconfig
 ;;

 abort-upgrade|abort-remove|abort-deconfigure)
 exit 0
 ;;

 *)
 echo "postinst called with unknown argument \`$1'" &gt;&amp;2
 exit 1
 ;;
esac

update-alternatives --install /usr/bin/fakeroot fakeroot /usr/bin/fakeroot-ng 5 \
 --slave /usr/share/man/man1/fakeroot.1.gz \
 fakeroot.1.gz /usr/share/man/man1/fakeroot-ng.1.gz

exit 0
</code></pre>

How would I use postinst script with fakeroot deb package builder

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

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

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

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

社区新版编辑器体验调研

下午好,我能够使用以下方法将我的项目构建成一个deb包：fakeroot dpkg-deb --build mypackage接下来，我可以使用dpkg -i mypackage.deb当我这样做时，所有的东西都被正确地安装和复制，但是我想在包安装之后运行一些bash命令。我知道这需要使用mypackage/DEBIA...

问如何在fakeroot deb包生成器中使用postinst脚本？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在fakeroot deb包生成器中使用postinst脚本？EN