I have an additional question on the same subject. We are migrating from poky 1.3, and I don't see any way I can start using the PR server (multi-site config, firewalled off, IT restrictions on running random network daemons, etc).
What is the solution for this case? -- Michael ________________________________________ From: [email protected] [[email protected]] On Behalf Of Bryan Evenson [[email protected]] Sent: Friday, November 07, 2014 7:31 AM To: [email protected] Subject: [oe] PRINC migration questions All, I am on poky/dylan and have not yet started using the PR server. I really do want to start using the PR server and stop using PRINC. However, even more so I really don't want to break my package feeds. I want to make sure I do my migration correctly and I don't do something that looks like it works okay only to find out it causes problems later. With that in mind, I am looking for advice on the proper way to migrate away from using PRINC. Let's say I have a .bbappend in my private layer with the line: PRINC := "${@int(PRINC) + 4}" The mainline layer's .bb has the line: PR = "${INC_PR}.0" And the mainline layer's .inc has the line: INC_PR = "r8" In this scenario, the resulting PR will be "r12.0". Now let's say I want to start using the PR server and get rid of PRINC in this recipe. The resulting package contents are to be the same, so I want the resulting PR to be "r12.0". From some limited testing, if I start the PR server and remove the PRINC line from my .bbappend the resulting PR is "r8.0". So in my .bbappend should I change the PRINC line to: INC_PR = "r12" Or should I change it to something else? If I change it to a hardcoded value, then I'll have to be careful about what to do if the mainline recipe changes INC_PR. How have other people handled this situation? Thanks, Bryan -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
