<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><font class="Apple-style-span" face="Courier">Hi William,</font><div><font class="Apple-style-span" face="Courier"><br></font><div><div><font class="Apple-style-span" face="Courier">Am 24.02.2009 um 23:48 schrieb William Bonnet:</font></div><blockquote type="cite"><div><font class="Apple-style-span" face="Courier">I am updateing my X11 libs packages in order to finally release these.<br><br>I have noticed that for some package the preinstall step is not executed in same case<br><br>I tested it on the x11/inputproto package.<br><br>If i run gmake clean && gmake package, then the pre-install target is never executed. But it i run gmake clean && gmake extract && gmake install then it is executed.<br><br>Is it a bug or a feature ? ;) Did i missed something or did something wrong ?<br></font></div></blockquote></div><font class="Apple-style-span" face="Courier"><br></font></div><div><font class="Apple-style-span" face="Courier">Difficult. In GAR v1 you had one flow in the Makefile:</font></div><div><font class="Apple-style-span" face="Courier"> checksum -> extract -> patch -> configure -> build -> test -> install -> package</font></div><div><font class="Apple-style-span" face="Courier">With GAR v2 you have</font></div><div><div><font class="Apple-style-span" face="Courier"> checksum -> extract -> patch -> configure -> build -> test -> install -> merge -> package</font></div></div><div><div><font class="Apple-style-span" face="Courier"> -> extract -> patch -> configure -> build -> test -> install -> merge -></font></div><div><font class="Apple-style-span" face="Courier"> -> extract -> patch -> configure -> build -> test -> install -> merge -></font></div><div><font class="Apple-style-span" face="Courier">That means the flow is split up for each modulation and then</font></div><div><font class="Apple-style-span" face="Courier">reunited before the package phase.</font></div><font class="Apple-style-span" face="Courier"><br></font></div><div><font class="Apple-style-span" face="Courier">Now a pre-install would mean "run pre-install before the first</font></div><div><font class="Apple-style-span" face="Courier">install is run". That would be easy. However, post-install as</font></div><div><font class="Apple-style-span" face="Courier">"run after the last install is run, but before the first merge"</font></div><div><font class="Apple-style-span" face="Courier">is somewhat difficult because invoking merge-modulation for</font></div><div><font class="Apple-style-span" face="Courier">one modulation would trigger install-modulated for all modulations</font></div><div><font class="Apple-style-span" face="Courier">to satisfy this condition.</font></div><div><font class="Apple-style-span" face="Courier"><br></font></div><div><font class="Apple-style-span" face="Courier">Thinking again I imagine that having general pre- and post-scripts for</font></div><div><font class="Apple-style-span" face="Courier">modulated rules outside the modulation is not really useful besides the</font></div><div><font class="Apple-style-span" face="Courier">edge-cases pre-extract and post-merge. I suggest changing the meaning</font></div><div><font class="Apple-style-span" face="Courier">of post-install to be what is currently post-install-modulated. During</font></div><div><font class="Apple-style-span" face="Courier">the transition warnings like this could be issued:</font></div><div><font class="Apple-style-span" face="Courier"><br></font></div><div><font class="Apple-style-span" face="Courier"> WARNING: 'pre-install-modulated' was called. The behaviour in mGAR v2</font></div><div><font class="Apple-style-span" face="Courier"> has changed. Please use 'pre-install' instead.</font></div><div><font class="Apple-style-span" face="Courier"><br></font></div><div><font class="Apple-style-span" face="Courier">I don't know how effectively modulations are used right now.</font></div><div><font class="Apple-style-span" face="Courier">Is this change straight forward or do I talk not-understandable</font></div><div><font class="Apple-style-span" face="Courier">stuff here? Thoughts?</font></div><div><font class="Apple-style-span" face="Courier"><br></font></div><div><font class="Apple-style-span" face="Courier"><br></font></div><div><font class="Apple-style-span" face="Courier">Best regards</font></div><div><font class="Apple-style-span" face="Courier"><br></font></div><div><font class="Apple-style-span" face="Courier"> -- Dago</font></div></body></html>