[meego-packaging] [meego-commits] 9438: Changes to Trunk:Testing/neon
nashif at linux.intel.com
Fri Nov 12 06:02:16 PST 2010
There is a big difference, since your home project does not build for ARM
So while it is a branch, it builds or can build against something wrong, it can be influenced by some WIP in your project and so on.
So the preferred way is really to have that isolated.
On 2010-11-12, at 1:44 PM, Patrick Ohly wrote:
> On Fr, 2010-11-12 at 13:33 +0000, ext-madhusudhan.3.nanjappa at nokia.com
>> Hmm.. You are right. I guess people usually branch with ..
>> Osc branch Trunk:Testing <package> -> this automatically created a home:<name>:branches:Trunk:Testing:pkg
>> In your case, I guess it was
>> Osc branch Trunk:Testing <package> <TGT-PRJ> -> this creates a branch
>> using the TGT_PRJ name you have specified, in this case it was
> Right. I wanted to avoid cluttering my home:pohly with extra
> sub-projects. But I can imagine that there might be one reason for
> requiring people to build in a "branches" sub project (different build
> settings), but that doesn't change the original problem: checking a
> submission based on the name of the source project alone is not
> For example, couldn't a clueless person like myself clone a package
> inside a branches:Trunk:Testing project instead of branching it?
> Anyway, I have now done the change the "normal" way and submitted from
> home:pohly:branches:Trunk:Testing. The usual question applies: where is
> that way documented?
> does not mention "branch" at all.
> Best Regards, Patrick Ohly
> The content of this message is my personal opinion only and although
> I am an employee of Intel, the statements I make here in no way
> represent Intel's position on the issue, nor am I authorized to speak
> on behalf of Intel on this matter.
More information about the MeeGo-packaging