<asdf28>
what do you do if you want to test some source code changes before compiling a package?
<asdf28>
is it possible to point the build system to an external source folder for a particular package?
Tobbi has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
fraggle_laptop has quit [Ping timeout: 272 seconds]
oblikoamorale has quit [Ping timeout: 256 seconds]
Tobbi has joined #libreelec
andy-burns has quit [Ping timeout: 240 seconds]
fraggle_laptop has joined #libreelec
andy-burns has joined #libreelec
moufl has quit [Quit: fuck it.]
moufl has joined #libreelec
andy-burns has quit [Ping timeout: 260 seconds]
JohnDoe_71Rus has joined #libreelec
anonymip has quit [Ping timeout: 265 seconds]
anonymip has joined #libreelec
LossAngeles has quit [Ping timeout: 244 seconds]
asdf28 has quit [Ping timeout: 256 seconds]
asdf28 has joined #libreelec
oblikoamorale has joined #libreelec
<chewitt>
asdf28 fork the sources and push the changes somewhere public and edit PKG_VERSION and PKG_SHA256 to use your version
<chewitt>
top tip .. if the upstream sources are on github and you forked there too, no need to change PKG_URL, it will magically find your version githash
<chewitt>
or use 'git format-patch' to generate a patch set that goes in the packages/section/packagenaame/patches subfolder.. and they are applied to the sources at build time
<chewitt>
the one thing you cannot do is point the package to a local filesystem folder; it's not how the buildsystem workss
asdf28 has quit [Ping timeout: 246 seconds]
ghostcube has joined #libreelec
asdf28 has joined #libreelec
held has joined #libreelec
<asdf28>
chewitt: thank you for the tips
<asdf28>
what i'm doing right now is creating my own .tar.gz of the source locally and generate a SHA256 of it
<asdf28>
but this gets tedious real fast after each change
<chewitt>
set PKG_SHA256=""
<chewitt>
it only validates if there's a value, so you can skip that bit
<chewitt>
and unless you're on dialup .. pushing changes to github and then updating the githash (only) is usually fastest
<chewitt>
unless the package is huge, then the patchset approach is easiest
<chewitt>
when I fiddle with kernels that are ~330MB to download .. I use a patchset
shibboleth has joined #libreelec
<chewitt>
when I fiddle with somethiing that's <=20MB I usually just push the changes to GitHub and update the githash in PKG_VERSION
<chewitt>
then GitHub handles making the tar files
<asdf28>
the patchset approach sounds great, thank you i'll try that