[FEA]: Instructions to compile this without docker infra
@shinzburh ci sta già lavorando.
Dal 9/10/2026.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 35/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Ferma
- Ambito
- build-system, devops
Direzione di ricerca
Iniziate leggendo gli script di build del repository infra che dipendono da Docker e lo script di build di nvmesh-management mostrato nell’issue, inclusi netinfo.spec e i comandi Poetry. Determinate quali sono gli input e gli output esistenti per infra/dist e come li utilizza il build RPM. Il lavoro è completato quando un normale comando shell Linux in infra crea tutti i file richiesti in infra/dist senza Docker.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Is this a new feature, an improvement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
Medium
Please provide a clear description of problem this feature solves
Based upon my reading of the build scripts inside the infra repo, they are heavily dependent upon docker based deployment. Our requirement is to build nvmesh-utils rpm, and we need:
- Build infra files in infra repo
- Copy them to rpm directory during rpm build triggered by nvmesh-management
- Build the RPM.
There is no involvement of docker in our build system while making rpm but infra build script as far as I could understand require docker envrionment for building infra. Currently as a workaround we are using the following type of shell script to compile infra from our fork of your nvmesh-management repo:
From nvmesh-management build script:
`INFRA_REPO="../nvmesh-infra"
if [ ! -d "$INFRA_REPO" ]; then
echo "Error: nvmesh-infra repo not found at $(cd .. && pwd)/nvmesh-infra"
echo "Clone it as a sister repo before building utils RPM."
exit 1
fi
export PATH="$HOME/.local/bin:/usr/local/bin:$PATH"
INFRA_WORKDIR=$(mktemp -d)
trap "rm -rf $INFRA_WORKDIR" EXIT
echo "Building infra CLI binary..."
( cd "$INFRA_REPO"
&& INFRA_DESCRIBE=$(git describe 2>/dev/null || echo "unknown")
&& sed -i "s#^(src_version:).*#\1 "${INFRA_DESCRIBE}"#" xlro/core/config/infra_config.yaml
&& echo "Stamping infra version: ${INFRA_DESCRIBE}"
&& poetry env use python${PYTHON_MAJOR_MINOR:-3.10}
&& poetry install --sync --no-interaction --no-root
&& export PYTHONDONTWRITEBYTECODE=1
&& rm -rf dist
&& poetry run pyinstaller netinfo.spec --log-level WARN --clean --workpath="$INFRA_WORKDIR" -y
) || { echo "Error: infra build failed"; exit 1; }
mkdir -p infrastructure/dist
# Copy the infra binaries we just built to destination folder for rpm packaging
cp -r "$INFRA_REPO"/dist/* infrastructure/dist/`
Longer term, we would like a simple script inside infra/ repo which we can call to compile all the files in $INFRA_REPO/dist/* without all the docker environment dependencies.
Feature Description
- As a developer trying to package infra/ files in nvmesh-utils rpm, I would like to be able to call a simple script or build command in infra/ repo to build all the files in $INFRA_REPO/dist/* folder.
- Once above functionality is there, we can remove extra code we added in our fork of nvmesh-management to compile infra. We can simply call the infra/ build script to make $INFRA_REPO/dist/* folder. Our build script can simply cp $INFRA_REPO/dist/* to rpm folder while packaging the rpm.
- RIght now since infra build is docker based and we are not using docker but just compiling rpms, we are having to duplicate infra build commands in nvmesh-management to compile infra dependency files.
Describe your ideal solution
- Call a build script in infra/ from normal linux shelll to compile the files in infra/dist/*.
Describe any alternatives you have considered
- For now we have a shell script in our nvmesh-management repo which builds infra for us.
- During code-review, its been stated to me that its not a great idea to duplicate build scripts from infra/ repo in our nvmesh-management code. If upstream can provide a way without docker dependency to compile infra/ binaries - that would avoid us the trouble of maintaining multiple build systems in the future.
Additional context
No response
Code of Conduct
- I agree to follow NVMesh's Code of Conduct
- I have searched the open feature requests and have found no duplicates for this feature request
- Lingua principale
- Python
- Stelle
- 12
- Fork
- 6
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
suitenumerique/accounts#160 ·
I maintainer di solito rispondono entro 1 giorno
-
Restoring an exhausted flatmap checkpoint can replay consumed recordsForse già presa @salma2vec l’ha presa oggi. Apertatype:bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
`ingest` fails with pynndescent 0.7Forse già presa @eroell l’ha presa oggi. ApertaTriage 🩺
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno