From: Stanislav Levin <slev@altlinux.org>
To: devel@lists.altlinux.org
Subject: Re: [devel] [librpm] обновление rpm и ldconfig
Date: Fri, 27 Sep 2019 09:39:25 +0300
Message-ID: <d42b45db-0eaa-f048-0951-5f9cf014fe53@altlinux.org> (raw)
In-Reply-To: <20190927012756.GA11167@altlinux.org>
[-- Attachment #1.1: Type: text/plain, Size: 988 bytes --]
>> Точно отсюда:
>>
>> http://git.altlinux.org/gears/r/rpm.git?p=rpm.git;a=blob;f=alt/rpm.spec;h=6200d5ccdc0dd8601b3f26da85995f4e213fce22;hb=3733d6dc0a531ef08e7dfd84e9da9bf813b895a6#l398
>>
>> 398 %triggerpostun -- rpm <=
>> 4.0.4
>>
>> 399 touch /var/lib/rpm/delay-posttrans-filetriggers
> %triggerpostun - это не файлтриггер.
>
> На самом деле RPM_INSTALL_NAME=rpm сперва попал в %post пакета rpm,
> оттуда в /usr/lib/rpm/pdeath_execute,
> оттуда в /usr/lib/rpm/postupdate,
> оттуда в /usr/lib/rpm/posttrans-filetriggers,
> оттуда в /usr/lib/rpm/0ldconfig.filetrigger.
>
В точных механизмах не разбирался. Но проверено на практике, что
отсутствие `%triggerpostun` напрямую или косвенно
влияет на RPM_INSTALL_NAME и RPM_INSTALL_ARG1 для RPM filetrigger (P8).
На самом деле это все детали, меня же интересует конкретная задача:
ожидать ли мне, что при обновлении с P8 на P9 отработает ldconfig?
закладываться ли на это?
Спасибо!
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-09-27 6:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 13:37 Stanislav Levin
2019-09-25 14:01 ` Dmitry V. Levin
2019-09-25 19:34 ` Stanislav Levin
2019-09-25 20:11 ` Dmitry V. Levin
2019-09-26 11:02 ` Stanislav Levin
2019-09-26 11:10 ` Dmitry V. Levin
2019-09-26 12:06 ` Anton Farygin
2019-09-26 12:23 ` Dmitry V. Levin
2019-09-26 13:00 ` Aleksei Nikiforov
2019-09-26 13:06 ` Dmitry V. Levin
2019-09-26 13:09 ` Stanislav Levin
2019-09-26 14:06 ` Anton Farygin
2019-09-26 14:29 ` Anton Farygin
2019-09-26 21:01 ` Stanislav Levin
2019-09-27 1:27 ` Dmitry V. Levin
2019-09-27 4:14 ` Anton Farygin
2019-09-27 6:39 ` Stanislav Levin [this message]
2019-09-27 11:49 ` Dmitry V. Levin
2019-09-30 9:22 ` Stanislav Levin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d42b45db-0eaa-f048-0951-5f9cf014fe53@altlinux.org \
--to=slev@altlinux.org \
--cc=devel@lists.altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
ALT Linux Team development discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
public-inbox-index devel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git