Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Figure out a better way to test externals #201

Open
supakeen opened this issue Sep 16, 2024 · 0 comments
Open

Figure out a better way to test externals #201

supakeen opened this issue Sep 16, 2024 · 0 comments

Comments

@supakeen
Copy link
Member

With the way we do external paths and the src-layout for the Python package combined with the Go externals it's a bit cumbersome to test things.

I created a stopgap to make external in #196, let's replace it with something better.
mvo5 added a commit to mvo5/osbuild-otk that referenced this issue Sep 25, 2024
@mvo5
Makefile: make python externals available without venv
6ede3ec 
To run the pyton externals currently a venv is needed. However
things work fine without except for this.

This commit tweaks the way the externals are made available so
that no venv is needed by just creating small wrapper binaries.

Followup for osbuild#204
Closes: osbuild#201 (at least for me)
@mvo5 mvo5 mentioned this issue Sep 25, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Makefile: make python externals available without venv mvo5/osbuild-otk
1 participant
@supakeen