doc: mention apt.txt in preparing.rst
See original GitHub issueYou should mention the use of an apt.txt
file in the documentation! It came handy for me to install gfortran
alongside a standard Python environment defined with a requirements.txt
file.
I would also add a note or mention the (advanced) possibility of using a Dockerfile
in preparing.rst
.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
doc: mention apt.txt in preparing.rst · Issue #41 · jupyterhub/binder ...
You should mention the use of an apt.txt file in the documentation! It came handy for me to install gfortran alongside a standard...
Read more >apt-get - APT package handling utility -- command-line interface
If a package is selected for installation (particularly if it is mentioned on the command line) and it could not be downloaded then...
Read more >"Unable to locate package" while trying to install ... - Ask Ubuntu
First, check if the package actually does exist: Go to packages.ubuntu.com with a web browser. Scroll down to "Search package directories".
Read more >Documentation » Installing Sphinx
Install either python3-sphinx using apt-get: $ apt-get install python3-sphinx. If it not already present, this will install Python for you.
Read more >Chapter 2. Debian package management
apt -get (8) for calling Debian package management system from scripts. It is also a fallback option ... The first document to read...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
thanks for bringing these kinds of issues! Not everybody opens documentation-related issues, but they are very helpful!
You know what I am going to say: could you make a PR to add a section about
apt.txt
? The only reason it is missing is that no one has gotten around to writing it down yet.Dockerfiles are covered in the next section of the docs. Maybe we need to rename the section titles a bit to make it more obvious that one follows after the other. Personally I am Ok with it being a bit difficult to discover that you can use a Dockerfile because it feels like in the past everyone was rushing to making their own, even when they didn’t have to. Debugging them is much harder and it is more complex to get right. So from that point of view persuading as many people as possible to not do it is a win for me. At the same time we want to know about people using Dockerfiles to see why it is they are using them so you can move things that are done across many Dockerfiles into a “supported mechanism” (like e.g. apt.txt)