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.

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

[wishlist] apt build-dep and source support #237

Open
yarikoptic opened this issue Nov 9, 2018 · 5 comments
Open

[wishlist] apt build-dep and source support #237

yarikoptic opened this issue Nov 9, 2018 · 5 comments
Labels

Comments

@yarikoptic
Copy link
Member

For me as a (Debian) developer I would love to be able to quickly get an environment (Dockerfile) given specification of not actual packages to be installed, but build-dependency packages and probably package sources to be installed. Immediate use cases:

  • give others a recipe to reproduce my build-environment if there is some bug to troubleshoot
  • quickly test building of a package while varying a set of installed packages

What it would entail is to

  • provide syntax to describe that for this package either use apt-get build-dep pkg or apt-get source pkg (would need some configuration option to decide where to dump those, default could be $HOME). Could be done via
    • a new value for -p: e.g. apt-bdep and apt-src to say for the following pkgs bdep or src are assumed.
    • or prefix before pkg name: e.g. "bdep:" and "src:" . I think this one is better since usually you do not need build-dependencies or sources for more than a single pkg, but you would like additional pkgs to get installed to ease troubleshooting. So I could say something like -p apt vim strace ncdu bdep:datalad src:datalad to install my helper tools, build-dependencies and sources of datalad pkg.
  • note that asking for build-dep requires apt-src, i.e. deb-src entries should be configured

Other managers could in principle/eventually acquire similar super powers (e.g. getting feedstock recipes for pkgs from conda-forge?)

@yarikoptic
Copy link
Member Author

again ran into this use case. Could not "pip install" linkchecker from a tarball failing with mysterious

    running build_ext
    error: [Errno 2] No such file or directory

which is all due to missing build dependencies for externals (e.g, gcc ;) ). Being able to enable apt sources and say to install bdep:linkchecker would have saved my day!

@djarecka
Copy link
Member

djarecka commented Feb 3, 2023

@yarikoptic - is it still a problem or could we close it?

@djarecka
Copy link
Member

@yarikoptic - I will close it now, but feel free to reopen if you still have the issue

@yarikoptic
Copy link
Member Author

came back to this desire/need in the scope of https://www.psychopy.org/download.html#pip-install where it seems I need to install build-depends of python3-wxpython, so thought "could neurodocker do that?"

@yarikoptic yarikoptic reopened this Aug 21, 2024
Copy link
Contributor

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants