[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Ltib] Modified packages using shared development
From: |
Mike Goins |
Subject: |
Re: [Ltib] Modified packages using shared development |
Date: |
Tue, 3 Feb 2015 13:14:22 -0500 |
On Thu, Jan 29, 2015 at 5:03 PM, Mathieu Rozon <address@hidden> 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
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/ltib
>
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Ltib] Modified packages using shared development,
Mike Goins <=