> To solve this problem for automated builds using buildbot, I added a > "--clobber" option to LTIB that removes a package's build directory if > the packages .spec file changes. The changes are pretty minimal; see > this thread: > > http://lists.gnu.org/archive/html/ltib/2011-01/msg00055.html
Wow, this is awesome. Just exactly what I need. Thanks! > Stuart, I understand the philosophy that unpacked source is never > clobbered, but in my/Mike's case where we are trying to use LTIB in > continuous integration systems, there is a need to be able to do this in > an automated manner, and "--clobber" is about the best I can think of... > >> Regards, Stuart >> >> On 15/02/12 00:00, Mike Goins wrote: >>> Wondering if anyone else has this particular type of situation. >>> >>> I setup a continuous integration system involving ltib. ltib also >>> builds kernel modules outside the source tree, so I have >>> PKG_KERNEL_LEAVESRC=y so the modules can build. But when the kernel >>> spec is updated, ltib refuses to colbber the existing kernel build >>> directory and apply the updated spec (usually new patches). >>> >>> I guess what I would like is if the the spec file is updated and ltib >>> detects a "directory build", is to go ahead and automatically clobber. >>> Now sure where I can make this modification to ltib. Or is there >>> some other way to accomplish this? >>> >> >> _______________________________________________ >> LTIB home page: http://ltib.org >> >> Ltib mailing list >> [email protected] >> https://lists.nongnu.org/mailman/listinfo/ltib > > > -- > Peter Barada > [email protected] > > > _______________________________________________ > LTIB home page: http://ltib.org > > Ltib mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/ltib _______________________________________________ LTIB home page: http://ltib.org Ltib mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/ltib
