Forcing fetch task when source changes

Forcing fetch task when source changes

[Vuille, Martin (Martin)]

[-- Attachment #1: Type: text/plain, Size: 329 bytes --]

I have defined a class with a customized fetch task (that
copies files from a local read-only directory to the ${S}
directory).

I am looking for a way to cause the fetch task to run
again whenever the contents of the local directory
change w.r.t. what was last fetched/copied to ${S}.

Is there a way to do that?

MV

[-- Attachment #2: Type: text/html, Size: 2261 bytes --]

Re: Forcing fetch task when source changes

[Burton, Ross]

On 22 September 2014 12:25, Vuille, Martin (Martin) <vmartin@avaya.com> wrote:
> I have defined a class with a customized fetch task (that
>
> copies files from a local read-only directory to the ${S}
>
> directory).
>
>
>
> I am looking for a way to cause the fetch task to run
>
> again whenever the contents of the local directory
>
> change w.r.t. what was last fetched/copied to ${S}.

Why not just use local URIs in the SRC_URI:

SRC_URI="file:///home/foo/bar/flob.c"

Ross

Re: Forcing fetch task when source changes

[Vuille, Martin (Martin)]

Would this work for a directory tree as opposed to a single file?

Also, the current "copy" is not a straight copy, it excludes certain files.
But I might be able to deal with that post-fetch.

MV


> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Sent: September 22, 2014 7:34 AM
> To: Vuille, Martin (Martin)
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Forcing fetch task when source changes
> 
> On 22 September 2014 12:25, Vuille, Martin (Martin) <vmartin@avaya.com>
> wrote:
> > I have defined a class with a customized fetch task (that
> >
> > copies files from a local read-only directory to the ${S}
> >
> > directory).
> >
> >
> >
> > I am looking for a way to cause the fetch task to run
> >
> > again whenever the contents of the local directory
> >
> > change w.r.t. what was last fetched/copied to ${S}.
> 
> Why not just use local URIs in the SRC_URI:
> 
> SRC_URI="file:///home/foo/bar/flob.c"
> 
> Ross

Re: Forcing fetch task when source changes

[Vuille, Martin (Martin)]

Perhaps I misunderstood your suggestion or I am missing
something obvious, but this doesn't work either.

If I point to my source with SRC_URI, the source does get
copied over to ${S} but changing the source doesn't trigger
a new fetch/unpack.

This is cleaner than what I was doing, but doesn't address
my issue of having to manually force a fetch/unpack every
time the source changes.

Perhaps due to my old versions: Poky 1.2 and bitbake 1.15.1?

MV


> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Sent: September 22, 2014 7:34 AM
> To: Vuille, Martin (Martin)
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Forcing fetch task when source changes
> 
> On 22 September 2014 12:25, Vuille, Martin (Martin) <vmartin@avaya.com>
> wrote:
> > I have defined a class with a customized fetch task (that
> >
> > copies files from a local read-only directory to the ${S}
> >
> > directory).
> >
> >
> >
> > I am looking for a way to cause the fetch task to run
> >
> > again whenever the contents of the local directory
> >
> > change w.r.t. what was last fetched/copied to ${S}.
> 
> Why not just use local URIs in the SRC_URI:
> 
> SRC_URI="file:///home/foo/bar/flob.c"
> 
> Ross

Re: Forcing fetch task when source changes

[Burton, Ross]

On 23 September 2014 13:46, Vuille, Martin (Martin) <vmartin@avaya.com> wrote:
> Perhaps due to my old versions: Poky 1.2 and bitbake 1.15.1?

Yes.

http://git.yoctoproject.org/cgit.cgi/poky/commit/meta/conf/bitbake.conf?id=eaf54b8dbf9371965b4ccf18609edeb8eee16144
is where the hashing was introduced to rebuild automatically when
inputs change, but that landed in 1.3 onwards.  The support was there
in 1.2 so you could try setting BB_SIGNATURE_HANDLER in your
distribution configuration to see if it works...

Ross

Re: Forcing fetch task when source changes

[Vuille, Martin (Martin)]

I was afraid of that...

Another good reason to upgrade.

Will try the work-around.

Thanks again!
MV

> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Sent: September 23, 2014 9:33 AM
> To: Vuille, Martin (Martin)
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Forcing fetch task when source changes
> 
> On 23 September 2014 13:46, Vuille, Martin (Martin) <vmartin@avaya.com>
> wrote:
> > Perhaps due to my old versions: Poky 1.2 and bitbake 1.15.1?
> 
> Yes.
> 
> http://git.yoctoproject.org/cgit.cgi/poky/commit/meta/conf/bitbake.conf?i
> d=eaf54b8dbf9371965b4ccf18609edeb8eee16144
> is where the hashing was introduced to rebuild automatically when inputs
> change, but that landed in 1.3 onwards.  The support was there in 1.2 so you
> could try setting BB_SIGNATURE_HANDLER in your distribution configuration
> to see if it works...
> 
> Ross

Re: Forcing fetch task when source changes

[Vuille, Martin (Martin)]

Very odd.

Our BSP vendor has configured BB_SIGNATURE_HANDLER to use OEBasicHash,
I see hashes in the stamp file names, if I change the metadata itself the change
is detected and the tasks are run again, but changing the content of a file named
in a "file://" SRC_URI has no effect.

Any ideas?

MV

> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Sent: September 23, 2014 9:33 AM
> To: Vuille, Martin (Martin)
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Forcing fetch task when source changes
> 
> On 23 September 2014 13:46, Vuille, Martin (Martin) <vmartin@avaya.com>
> wrote:
> > Perhaps due to my old versions: Poky 1.2 and bitbake 1.15.1?
> 
> Yes.
> 
> http://git.yoctoproject.org/cgit.cgi/poky/commit/meta/conf/bitbake.conf?i
> d=eaf54b8dbf9371965b4ccf18609edeb8eee16144
> is where the hashing was introduced to rebuild automatically when inputs
> change, but that landed in 1.3 onwards.  The support was there in 1.2 so you
> could try setting BB_SIGNATURE_HANDLER in your distribution configuration
> to see if it works...
> 
> Ross

Re: Forcing fetch task when source changes

[Burton, Ross]

On 23 September 2014 16:46, Vuille, Martin (Martin) <vmartin@avaya.com> wrote:
> Very odd.
>
> Our BSP vendor has configured BB_SIGNATURE_HANDLER to use OEBasicHash,
> I see hashes in the stamp file names, if I change the metadata itself the change
> is detected and the tasks are run again, but changing the content of a file named
> in a "file://" SRC_URI has no effect.
>
> Any ideas?

None, sorry.  Possibly you've found a bug in the 1.2-era hashing code.
Can you lean on your BSP provider to stop using 2.5 year old releases?
:/

Ross

Re: Forcing fetch task when source changes

[Vuille, Martin (Martin)]

We're planning an update to Dizzy, and to keep up-to-date after that.

Thanks for your help
MV

> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Sent: September 26, 2014 5:55 PM
> To: Vuille, Martin (Martin)
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Forcing fetch task when source changes
> 
> On 23 September 2014 16:46, Vuille, Martin (Martin) <vmartin@avaya.com>
> wrote:
> > Very odd.
> >
> > Our BSP vendor has configured BB_SIGNATURE_HANDLER to use
> OEBasicHash,
> > I see hashes in the stamp file names, if I change the metadata itself
> > the change is detected and the tasks are run again, but changing the
> > content of a file named in a "file://" SRC_URI has no effect.
> >
> > Any ideas?
> 
> None, sorry.  Possibly you've found a bug in the 1.2-era hashing code.
> Can you lean on your BSP provider to stop using 2.5 year old releases?
> :/
> 
> Ross