[meta-freescale] Patch - udev_173.bbappend

[Lewis, Nick]

>> Otavio
>>
>> May I please request the following patch. It has two purposes - it
>> changes the protocol used by the git fetcher to use the universally
>> available http protocol
>
>I understand but other recipes also use git:// protocol so this wouldn't fix it for others.
>And in fact it is not really a problem but a network issue.
>
>How you fixed it for the other recipes?
>
There are only two other fsl-image-test recipes that fetch from a git repository with the git protocol so at the user layer I do:

$ cat meta-nick/recipes-multimedia/v4l-apps/v4l-utils_0.8.8.bbappend
PRINC := "${@int(PRINC)+1}"
SRC_URI := "${@oe_filter_out('git://linuxtv.org/v4l-utils.git;protocol=git', '${SRC_URI}', d)}"
SRC_URI =+ "git://linuxtv.org/git/v4l-utils.git;protocol=http"

$ cat meta-nick/recipes-benchmark/fio/fio_2.0.5.bbappend
PRINC := "${@int(PRINC)+1}"
SRC_URI .= ";protocol=http"
nicklewis at ubuntu:/data/yocto/rootfs_builder/sources$

>> and it removes the use of SRC_URI_prepend which is problematic for user layers on top of meta-fsl-arm:
>
>What problem you had with the prepend?
>

The problem is the way in which _prepend operates as opposed to =. or =+ (ditto _append vs .= or +=)
The _prepend mechanism operates *whenever* there is an assignment to the variable so a high priority layer that wishes to change the value of the variable is still affected by a _prepend from a lower priority layer. There is apparently no way to _unprepend what a previous layer has _prepended

example:

# fsl layer priority 5
SRC_URI = "fsl-selected-uri"
SRC_URI_prepend = "fsl-selected-prefix "

# user layer priority 6 appended afterwards
SRC_URI_prepend = ""
SRC_URI = "user-selected-uri"

bitbake -e shows SRC_URI is unhelpfully set to "fsl-selected-prefix user-selected-uri"

--
Nick

The details of this company are as follows:
G4S Technology Limited, Registered Office: Challenge House, International Drive, Tewkesbury, Gloucestershire GL20 8UQ, Registered in England No. 2382338.

This communication may contain information which is confidential, personal and/or privileged.

It is for the exclusive use of the intended recipient(s).
If you are not the intended recipient(s), please note that any distribution, forwarding, copying or use of this communication or the information in it is strictly prohibited.

Any personal views expressed in this e-mail are those of the individual sender and the company does not endorse or accept responsibility for them.

Prior to taking any action based upon this e-mail message, you should seek appropriate confirmation of its authenticity.

This e-mail has been scanned for all viruses by MessageLabs.