From: Katu Txakur <katutxakurra@gmail.com>
To: yocto@yoctoproject.org
Subject: Re: Perforce fetcher ignores module and label
Date: Wed, 2 Aug 2017 08:40:10 +0100 [thread overview]
Message-ID: <CAM1ZcoUYPs_TRwcCT=_9o6pWO1XDpmaRUuTZn=X1O5qkPkY3Eg@mail.gmail.com> (raw)
In-Reply-To: <CAM1ZcoVg_NuFbLkAHCRJmXAhX7g9EA04h+9NYmWb9QAJWCcnKA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]
Hi,
I'm still having problems fetching from Perforce. Is there any
documentation based on the latest implementation of the
poky/bitbake/lib/bb/fetch2/perforce.py file?
The copyright 2016 points to Kodak Alaris, Inc. Should I contact them?
I would appreciate if someone could point me in the right direction.
Regards,
Katu
2017-07-25 10:05 GMT+01:00 Katu Txakur <katutxakurra@gmail.com>:
> Hi,
>
> I'm upgrading a recipe that fetches the source code from Perforce.
>
> The old recipe was:
>
> SRC_URI = " \
> p4://${P4USER}:${P4PASSWD}:${P4HOST}:${P4PORT}@Depot/path/pe
> rforce/...;module=local/path/relativeto/p4;label=${P4CHANGELIST} \
> "
>
> With the new version of /lib/bb/fetch2/perforce.py, I had to set P4PORT
> outside SRC_URI, leaving the recipe with:
>
> SRC_URI = " \
> p4://${P4USER}:${P4PASSWD}@Depot/path/perforce/...;module=
> local/path/relativeto/p4;label=${P4CHANGELIST} \
> "
>
> The Perforce fetcher kind of works, but it seems to be ignoring the
> "module" and the "label" attributes. After reading the Python script I can
> see that after the "@", only the substring before the first ";" is used.
>
> Is there a way to set module and label/changelist? I have several folders
> per recipe that I need to map to different subfolders and with the current
> script some of the folders don't get fetched.
>
> Thanks for your time.
>
> Regards,
> Katu
>
[-- Attachment #2: Type: text/html, Size: 2118 bytes --]
next prev parent reply other threads:[~2017-08-02 7:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 9:05 Perforce fetcher ignores module and label Katu Txakur
2017-08-02 7:40 ` Katu Txakur [this message]
2017-08-02 8:28 ` Paul Eggleton
2017-08-02 9:51 ` Katu Txakur
2017-08-07 11:17 ` Andrew Bradford
[not found] ` <CAM1ZcoX7ee=hCBYqWPQoeg_wrWjzqqbZvsrTm12sfZc2Fe0JJQ@mail.gmail.com>
2017-08-11 12:52 ` Andrew Bradford
2017-08-28 7:56 ` Katu Txakur
2017-08-28 14:27 ` Andrew Bradford
2017-08-28 16:43 ` Katu Txakur
2017-08-31 17:54 ` Andrew Bradford
2017-09-14 10:13 ` Katu Txakur
2017-09-14 16:17 ` Andrew Bradford
2017-09-18 10:32 ` Katu Txakur
2017-09-18 15:41 ` Katu Txakur
-- strict thread matches above, loose matches on Subject: below --
2017-07-06 14:24 Katu Txakur
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAM1ZcoUYPs_TRwcCT=_9o6pWO1XDpmaRUuTZn=X1O5qkPkY3Eg@mail.gmail.com' \
--to=katutxakurra@gmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.