Dualing downloads
If I have a package X that depends on X-native and they build from the same sources, doesn't the fetch step duplicate effort if the sources need to be downloaded from scratch? I just saw this [appear to] happen and it's not clear if the sources were downloaded once or twice.
I this is the case, perhaps if X depends on X-native then X.fetch should depend on X-native.fetch so then download happens only once? Or is that too hard to detect?
For many packages (and fast network links) this probably isn't an issue, but I could imagine some very large packages simply wasting network bandwidth.
Note: I'm happy if I'm wrong about this, it just jumped out at me.
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 5 lines · Gary Thomas
If I have a package X that depends on X-native and they build from the same sources, doesn't the fetch step duplicate effort if the sources need to be downloaded from scratch? I just saw this [appear to] happen and it's not clear if the sources were downloaded once or twice.
The first one should create the lock file and second fetch task should just reuse the already downloaded source.
Otherwise sharing whole downloads directory between multiple builders wouldn't work as well.
Quoted 20 lines
I this is the case, perhaps if X depends on X-native then X.fetch should depend on X-native.fetch so then download happens only once? Or is that too hard to detect?
For many packages (and fast network links) this probably isn't an issue, but I could imagine some very large packages simply wasting network bandwidth.
Note: I'm happy if I'm wrong about this, it just jumped out at me.
Signature · 9 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ -- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
Quoted 7 lines · Martin Jansa
Quoted 5 lines · Gary Thomas
If I have a package X that depends on X-native and they build from the same sources, doesn't the fetch step duplicate effort if the sources need to be downloaded from scratch? I just saw this [appear to] happen and it's not clear if the sources were downloaded once or twice.
Quoted 6 lines
The first one should create the lock file and second fetch task should just reuse the already downloaded source.
Otherwise sharing whole downloads directory between multiple builders wouldn't work as well.
That's great, thanks
Quoted 9 lines
Quoted 9 lines
I this is the case, perhaps if X depends on X-native then X.fetch should depend on X-native.fetch so then download happens only once? Or is that too hard to detect?
For many packages (and fast network links) this probably isn't an issue, but I could imagine some very large packages simply wasting network bandwidth.
Note: I'm happy if I'm wrong about this, it just jumped out at me.
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------