brewkit
brewkit copied to clipboard
pkgxdev
build infra & `$ pkg build`
When building (`bk build ...`) a python project using python-venv.py, I see this output in the terminal. ``` DEBUG:root:+TMPDIR=/Users/u0076374/_/pkgx/repos/pantry_mag/builds/github.com__univ-of-utah-marriott-library-apple__jctl-1.1.21/dev.pkgx.python.build bin/pip install /Users/u0076374/_/pkgx/repos/pantry_mag/builds/github.com__univ-of-utah-marriott-library-apple__jctl-1.1.21 --verbose --no-clean --require-virtualenv Using pip 23.2.1 from /opt/pkgx/github.com/univ-of-utah-marriott-library-apple/jctl/v1.1.21+brewing/venv/lib/python3.12/site-packages/pip...
trying to exclude a test for a specific version of jenkins.io; this should work: ```yaml - run: jenkins-lts --version | grep {{version}} if: '2.426.3' ``` but doesn't. indeed, even this...
Is there a way to set up different URLs for each platform (Darwin/Linux)? something along the way: ``` distributable: darwin: url: https://github.com/pkgxdev/darwin/brewkit/archive/refs/tags/v{{ version }}.tar.gz linux: url: https://github.com/pkgxdev/linux/brewkit/archive/refs/tags/v{{ version }}.tar.gz ```
I am encountering an issue when attempting to create a package using a private GitHub repository in the PkgX Pantry. When trying to build getting **404 error** for the repo.
When tea installs a package it would be nice if it included some sort of metadata dotfile in the install dir, perhaps called `.tea-meta`. This could be useful for a...
Of interest is their encoding full versions for deps: ``` CMake Error in CMakeLists.txt: Imported target "sodium" includes non-existent path "/Users/jacob/.tea/libsodium.org/v1.0.18/include" in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include: * The path...
The following fails (go.dev-type): ```yaml build: working-directory: src script: - make.bash - mkdir -p "{{prefix}}" - run: mv src "{{prefix}}" working-directory: $SRCROOT ``` with ```shell + unset OLDWD + OLDWD=/var/folders/8b/n_gmhmk57ks85swq3mrdbrwc0000gp/T/1892f004/src...
One thing I've noticed about making packages is that when there are errors it's hard to know exactly where I should go hacking. The reason why is because I know...
we could speed up a whole bunch of stuff if eg. the pip/cargo cache wasn't blown away every time. we reassign HOME, thus the caches go there. perhaps symlinking these...
