http://bugzilla.suse.com/show_bug.cgi?id=983529 http://bugzilla.suse.com/show_bug.cgi?id=983529#c2 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger@suse.com, | |trenn@suse.com Flags| |needinfo?(trenn@suse.com) --- Comment #2 from Josef Reidinger --- Hi Thomas, good question. I checked code and possible values are - "insts-sys" in live installer or common installer ( including autoyast installation) - "yes" for other cases when yast runs Reason why it exists is optimization of installation. There is many packages that do repetive work like creating initrd. So if there is conclusion to do it only once during installation, then such post install script check if it is in installation and do not run command and then run it once at the end of installation. Now after stopped using SuSE-config scripts, I am aware mainly only about mkinitrd creation and updating bootloader configuration that use it as it is time consuming, so it done only once at the end of installation when yast ensure that proper bootloader configuraiton is used and brand new initrd is generated with all specific modules included if needed. I hope it answers your question. Regarding documentation, I have question for you, where you expect such documentation? Then I can add it there. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=983529 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(jreidinger@suse.c | |om) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=983529 http://bugzilla.suse.com/show_bug.cgi?id=983529#c5 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jreidinger@suse.c | |om) | --- Comment #5 from Josef Reidinger --- (In reply to Thomas Renninger from comment #3)

A lot of packages who need regeneration of initrd on install or update have or had such a code snippet in their %post section:

if [ "${YAST_IS_RUNNING}" != "instsys" ]; then if [ -e %{_localstatedir}/lib/no_initrd_recreation_by_suspend ]; then echo "Skipping recreation of existing initial ramdisks, due" echo "to presence of %{_localstatedir}/lib/no_initrd_recreation_by_suspend" %if %{defined regenerate_initrd_post} else %regenerate_initrd_post

Could you check whether this is still needed, please.

Yes, it is still very useful as it speed up installation. As I described above, yast2-bootloader will recreate initrd after rpm was installed. And since initrd creation is expensive and often done more then once in post install scripts, then such check speed up installation.

I like to get totally rid of this and only have: %regenerate_initrd_post to handle initrd re-creation. Either by simply removing the "${YAST_IS_RUNNING} and -e %{_localstatedir}/lib/no_initrd_recreation_by_suspend" code or by moving it into the %regenerate_initrd_post macro.

Using macro for that task make sense for me.

Still documenting ${YAST_IS_RUNNING} would be a good idea. There are not many users, but some. I would recommend to put it here: /usr/lib/rpm/suse_macros This is where I would have found it...

OK, I think it make sense to document it in our wiki or on our yast project page and then put to /usr/lib/rpm/suse_macros just link as there are more users of them ENV variable. -- You are receiving this mail because: You are on the CC list for the bug.