On Wed, 19 Aug 2015, Alan McKinnon wrote: > On 19/08/2015 21:58, Alec Ten Harmsel wrote: > > On Wed, Aug 19, 2015 at 08:55:16PM +0100, Mick wrote: > >> On Wednesday 19 Aug 2015 10:28:48 Jeremi Piotrowski wrote: > >>> Smart live rebuild only deals with live ebuilds. How would it help in this > >>> case? > >> > >> Anyone cares to explain what is a "live ebuild"? > >> > >> Then I may be able to understand what @smart-live-rebuild may be useful > >> for. > >> :-/ > >> > >> -- > >> Regards, > >> Mick > > > > A "live ebuild" is an ebuild that pulls the code to build straight from > > whatever version control the developers are using, so you always have > > the latest and greatest. > > > > Alec > > > > > they usually have version number -9999 >
portage has no way of knowing if the repository the package comes from has been updated without fetching the sources and this is done during the merge process. So portage has no knowledge of the state of live-ebuild packages prior to starting a merge - it doesn't know if they have been updated upstream, so it does nothing to them during normal updates. To update them you can use the set @live-rebuild. But this causes live packages to be unconditionally rebuilt even if they haven't changed. Smart-live-rebuild deals with this by updating the repositories and then only re-emerging packages that have been changed.
