On Thu, Jan 29, 2015 at 5:03 PM, Mathieu Rozon <[email protected]> wrote: > Hi, > > > > I did minor modifications to packages kobs-ng and imx-bootlets. > > We are multiple people working on this project and are using Git to share > our code. > > For the imx-bootlets package, simply adding the source code without scbuild > and scdeploy works fine when the developer builds ltib. > > My issue is with the kobs-ng package. If I could create and upload a patch > everything would should build without problem, but I am trying to find an > alternative. > > > I know that before building ltib, I should execute scbuild and scdeploy on > the package, but this creates files with absolute paths relative to my build > platform not corresponding to the other developers. > > > > If I could force ltib to run scbuild and scdeploy on the kobs-ng package > when executing ltib it would also solve my problem. > > > > Maybe there is also a simpler solution that I simply do not see…
If you don't check-in your generated rpms, ltib detects the spec file is newer than the rpm and rebuilds that rpm locally. Is that the issue? Don't quite follow. > > > Thank you > > > > - Mat - > > > > > > > > > > > _______________________________________________ > 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
