summaryrefslogtreecommitdiff
path: root/include/release.sh
AgeCommit message (Collapse)Author
2025-05-26release.sh: use printf to create version filesLeah Rowe
Don't copy the files directly, because we might be doing this from a work directory that has no files; in this case, generic "unknown" variables are used, without generating any files, so the current logic would produce an error. However, we do need to create those dot files, because we then rely on them for building release binaries. The new logic maintains current behaviour, while fixing this technical edge-case scenario via mitigation. Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-26xbmk: rename xbmklocal/xbmktmp variablesLeah Rowe
shorten them Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-22release.sh: copy version files to rsrcLeah Rowe
Otherwise, an "unknown" version number is created. This regression was caused by the recent optimisation that reduces the amount of extra work done by init.sh on child instances of xbmk. As a result of those changes, now release.sh has to do some minor initialisation of its own, such as this. Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-18release.sh: rename relsrc to rsrcLeah Rowe
Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-18release.sh: tidy up nuke()Leah Rowe
i wasn't ok having that variable initialisation and then the commands on the same line. it looks messy. having the commands on a separate line makes the code nice to read, so let's separate them. Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-17release.sh: simplify nuke() EVEN MORE, yet againLeah Rowe
Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-17release.sh: use x_ on find command for nuke()Leah Rowe
Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-17release.sh: simplify nuke() EVEN MORELeah Rowe
Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-17get.sh: move nuke() to release.shLeah Rowe
we really only need it there, because the context is for release archives. normal use of the git repository doesn't matter in the context of deletions, because that will not be distributed. only the result of ./mk release will be distributed. the builds produced will not change as a result of this, for people using the normal git repository, because the files in question are never used anyway, in our configs. this is being done to make working on local repos easier. Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-17release.sh: simplify prep_release_bin()Leah Rowe
Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-17release.sh: don't move src/docs/Leah Rowe
otherwise, ./mk -b (without argument) will fail, on release archives. also, perhaps i should add an mkhelper to build it? Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-13release.sh: Don't run prep_release with fx_Leah Rowe
The result of the printf statement is sorted, making it do binaries first, which results in a lot of junk files then being present inside the source archive. Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-12release.sh: simplify release()Leah Rowe
Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-12release.sh: clean up the vdir after releaseLeah Rowe
do this after moving the version directory within it. Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-12release.sh: remove src_dirname variableLeah Rowe
Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-12release.sh: build in tmp directory firstLeah Rowe
don't move to the real directory until the work is done. that way, a re-try can be done, while analysing the old files. it is created based on the tmpdir, under XBMK_CACHE/ Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-12release.sh: remove unnecessary mkdir commandLeah Rowe
the following git clone command creates that directory Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-12release.sh: split up build_release()Leah Rowe
Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-12release.sh: delete tmp/cache from the tarballLeah Rowe
Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-12lib.sh: remove rmgit()Leah Rowe
We don't need to call it from git.sh, because it's only being done when building a release anyway, and we already run rmgit when doing a release. The function itself is only two simple fx_ calls, so we can just do that from build_release(). Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-12lib.sh: remove mk()Leah Rowe
i don't need it. i can use fx_ instead, on functions that previously called mk(). Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-09lbmk: use x_ instead of err, where appropriateLeah Rowe
many places in lbmk used err, because older versions of x_ did not handle globbing properly. however, use of x_ is preferable on trivial commands. the only time err() should be called is what it has to be, when x_ can't work, or when a more useful error message is needed, for context. Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-08mk: move release functions to idnclude/release.shLeah Rowe
The idea with mk is that it's meant to basically be a stub for running everything else, while mainly having the trees logic within it (what was once script/trees). Signed-off-by: Leah Rowe <leah@libreboot.org>