<p>Ar 24 DFómh 2011 ag 16:38, scríobh "Thomas Petazzoni" <<a href="mailto:thomas.petazzoni@free-electrons.com">thomas.petazzoni@free-electrons.com</a>>:<br>
><br>
> * Tracking of files installed by packages. Do we care ? Is this an<br>
> important feature of Buildroot ? Won't the added complexity make<br>
> Buildroot more complicated to understand ?<br>
><br>
> Which solution ? Two solutions:<br>
><br>
> - Change the installation steps of packages so that each package<br>
> installs in a different directory.<br>
><br>
> Pros:<br>
><br>
> seems to be the cleanest solution.<br>
><br>
> allows to easily detect packages overriding files installed by<br>
> other packages.<br>
><br>
> Cons:<br>
><br>
> requires modifications of all gentargets packages to use<br>
> $$(STAGING_DIR) and $$(TARGET_DIR) instead of $(STAGING_DIR)<br>
> and $(TARGET_DIR).<br>
></p>
<p>Hello all,<br>
A few months back I posted a patch set that provided a primitive, but functional, first attempt at this feature (as a separate target install stage in addition to the existing method) after being prompted to share by Yann. I don't think I saw any response but I do remember ThomasP saying on IRC that it was too simplistic and that he would comment in detail on the list but it seems to have fallen off his (long) list of tasks.<br>
I might take this opportunity to ask for comment again. One thing is that it needed no extra $ on TARGET_DIR for gen-/auto-targets. The value of TARGET_DIR is simply overridden to be "output/package/$package".</p>
<p>The reason I "care" about this kind of thing is to allow packaging of the build components for separate download to the target. I doubt I'm the only one with such a need - never mind the possibility of package uninstall and other as yet unconsidered purposes.<br>
</p>