chromium: Don't add sources as runtime dependency.
This is because of a single file that symlinks to the source output path: libexec/chromium/resources/extension/demo/library.js Target within source output path: chrome/browser/resources/extension_resource/demo/library.js So we just need to ensure that the cp command follows symlinks during installPhase and we should no longer have this unnecessary dependency. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This commit is contained in:
parent
0c50978cb8
commit
3ae3f3272f
@ -11,7 +11,7 @@ mkChromiumDerivation (base: rec {
|
|||||||
ensureDir "$libExecPath"
|
ensureDir "$libExecPath"
|
||||||
cp -v "$buildPath/"*.pak "$libExecPath/"
|
cp -v "$buildPath/"*.pak "$libExecPath/"
|
||||||
cp -v "$buildPath/icudtl.dat" "$libExecPath/"
|
cp -v "$buildPath/icudtl.dat" "$libExecPath/"
|
||||||
cp -vR "$buildPath/locales" "$buildPath/resources" "$libExecPath/"
|
cp -vLR "$buildPath/locales" "$buildPath/resources" "$libExecPath/"
|
||||||
cp -v $buildPath/libffmpegsumo.so "$libExecPath/"
|
cp -v $buildPath/libffmpegsumo.so "$libExecPath/"
|
||||||
|
|
||||||
cp -v "$buildPath/chrome" "$libExecPath/$packageName"
|
cp -v "$buildPath/chrome" "$libExecPath/$packageName"
|
||||||
|
Loading…
x
Reference in New Issue
Block a user