Sounds like there is a bit of a conceptual error in how our build and
packaging system works.
Do NOT add patches to the packaging/ directory. Do submit patches to
the tizen branch that directly changes the files.
The backend will extract a set of patches, using the upstream branch as
pristine (which is why there is no packaging directory on that branch)
along with appropriate tags, to create a source rpm that looks includes
a pristine tarball with a set of patches.
--rusty
On Tue, 2013-10-15 at 04:38 +0000, RAVI NANJUNDAPPA wrote:
> hi Junfeng,
>
>
>
> Thanks for that quick information.
>
> Well... I was looking into the "upstream" branch of the gcc48 git
> project.
>
> Just now I checked out the "tizen" branch of the git source and I was
> able to see the packaging directory.
>
> I was thinking I should add the .patch file into the packaging
> directory as we can see in
> https://build.tizen.org/package/show?package=gcc48&project=Tizen and
> update the spec file with the patch files.
>
> But the packaging directory in the checkout git source, doesn't list
> any of the .patch files and even the spec file with the patch
> commands.
>
> I was wondering why there is such a descrepancy in the packaging
> directory contents from OBS and git sources.
>
>
>
>
>
> Thanks and Best Regards,
>
> N Ravi
>
> ------- Original Message -------
>
> Sender : Dong, Junfeng<[email protected]>
>
> Date : Oct 15, 2013 09:27 (GMT+05:30)
>
> Title : RE: [Dev] regarding process for patch submission when there is
> no packaging dir for tizen upstream projects
>
>
>
> Hi Ravi,
>
> I have submitted some changes to gcc48 project, and doesn’t run into
> the problem you mentioned.
>
> Are you using the “tizen” branch? “packaging” dir is there. And could
> you should me you change and the push command?
>
> Thanks
>
> Junfeng
>
> From: [email protected] [mailto:[email protected]]
> On Behalf Of RAVI NANJUNDAPPA
> Sent: Tuesday, October 15, 2013 11:51 AM
> To: [email protected]
> Cc: [email protected]
> Subject: [Dev] regarding process for patch submission when there is no
> packaging dir for tizen upstream projects
>
>
>
>
> Hi All,
>
>
>
> I would like to submit a change for gerrit review request of
> "platform/upstream/gcc48" gerrit project.
> It include a patch and spec file changes.
> Since there is no packaging dir in the above git path after doing a
> git clone, I couldn't find a way to git push the spec and patch
> changes.
>
> I followed the "Building using upstream tarball and patch generation"
> section of
> https://source.tizen.org/documentation/reference/git-build-system/upstream-package.
>
> But gbs export gave a consolidated changes along with mine ( after
> updating the source changes), which doesn't clearly identify my
> changes.
>
> So, kindly provide your inputs/steps to be followed which will be very
> much required for the change submission.
>
>
> Thanks and Best Regards,
>
> N Ravi
>
>
>
>
>
>
>
> Image removed by sender.
>
>
>
>
>
>
>
> _______________________________________________
> Dev mailing list
> [email protected]
> https://lists.tizen.org/listinfo/dev
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
