search for: pypi_pkg

Displaying 3 results from an estimated 3 matches for "pypi_pkg".

Did you mean: pypi_pkgs
2023 Mar 01
2
[nbdkit PATCH 0/5] ci: Get to green status on FreeBSD and MacOS
...| 11 ++++++++--- > ci/manifest.yml | 20 +++++++++++++++----- > 7 files changed, 68 insertions(+), 11 deletions(-) > series Acked-by: Laszlo Ersek <lersek at redhat.com> One question (for my understanding) about the context of patch#1: -e "s|[@]PYPI_PKGS@|$PYPI_PKGS|g" what's this [@] notation? Why do we need to sink the at-sign into a bracket expression? Thanks Laszlo
2023 Mar 01
1
[nbdkit PATCH 0/5] ci: Get to green status on FreeBSD and MacOS
...> > 7 files changed, 68 insertions(+), 11 deletions(-) > > > > series > Acked-by: Laszlo Ersek <lersek at redhat.com> Thanks; now in as 99c57eef..648a7909 > > One question (for my understanding) about the context of patch#1: > > -e "s|[@]PYPI_PKGS@|$PYPI_PKGS|g" > > what's this [@] notation? Why do we need to sink the at-sign into a > bracket expression? In the context of this patch, copy-and-paste from existing paradigm. More historically, I can think of two possible sources, both from GNU heritage: For a project using...
2023 Mar 01
7
[nbdkit PATCH 0/5] ci: Get to green status on FreeBSD and MacOS
I took the easy route of crippling what I couldn't get working, on the grounds that partial coverage is better than none now that we have Cirrus CI checking commits on additional platforms. This series got me to a green checkmark: https://gitlab.com/ebblake/nbdkit/-/pipelines/793156983 but depends on an as-yet uncommitted patch in libvirt-ci: