[oe] RFC One recipe with two git repository as sources
Mark Hatle
mark.hatle at windriver.com
Thu Jun 23 14:37:28 UTC 2011
On 6/23/11 9:25 AM, Phil Blundell wrote:
> On Thu, 2011-06-23 at 13:36 +0200, Holger Freyther wrote:
>> On 06/23/2011 01:21 PM, Phil Blundell wrote:
>>> On Thu, 2011-06-23 at 13:18 +0200, Holger Freyther wrote:
>>>> - destdir = os.path.join(destdir, "git/")
>>>> + destsuffix = ud.parm.get("destsuffix", "git/")
>>>> + print destsuffix
>>>> + destdir = os.path.join(destdir, destsuffix)
>>>
>>> I think that "print" might be extraneous, but other than this your patch
>>> looks awesome. I think this would resolve the problem that I was having
>>> in.
>>
>> great, yeah the print is bogus and the question if and how this applies to
>> fetch/git.py is also unresolved (i had a quick look but have not found the
>> dirname it uses to create the tarball).
>
> I'm not entirely clear on what's going on with fetch vs fetch2 at all,
> in terms of whether fetch is going away at some point or the two of them
> are meant to be existing in parallel. Can one of the TSC überhackers
> shed any light on what the intent is there?
>
"fetch" is remaining for compatibility for the time being. I believe the intent
is that fetch will go away when compatibility is no longer needed or desired.
--Mark
> p.
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
More information about the Openembedded-devel
mailing list