If you are on Unix, you could use the access time of the files in there. Just enable access time for your filesystem, then run a clean build of all your projects you would like to keep dependencies for and then do something like this (UNTESTED!): find ~/.m2 -amin +5 -iname ‘*.pom’ | while read … Read more
Peer dependency warnings, more often than not, can be ignored. The only time you will want to take action is if the peer dependency is missing entirely, or if the version of a peer dependency is higher than the version you have installed. Let’s take this warning as an example: npm WARN @angular/animations@5.2.1 requires a … Read more
This is not possible, and likely never will be because it would be rather heavy-handed for RubyGems to allow gem developers to require that users have a specific version control system installed to access a gem. Gems should be self-contained with a minimal number of dependencies so that people can use them in as wide … Read more
You may defer the import, for example in a/__init__.py: def my_function(): from a.b.c import Blah return Blah() that is, defer the import until it is really needed. However, I would also have a close look at my package definitions/uses, as a cyclic dependency like the one pointed out might indicate a design problem.
Yes, MANIFEST.in and setup.py should be sufficient. This blog post really has some good information on this topic: Packaging a Django reusable app And here’s another good, detailed overview that helped me a lot: Python Packaging User Guide Especially the tips to get your static files (templates) included are important as this might not be … Read more
For the quick reader : this QA is about the package.json bundledDependencies field, not about the package. What bundledDependencies do “bundledDependencies” are exactly what their name implies. Dependencies that should be inside your project. So the functionality is basically the same as normal dependencies. They will also be packed when running npm pack. When to … Read more
Not possible. Maven checks the repositories in their declaration order until a given artifact gets resolved (or not). Some repository manager can do something approaching this though. For example, Nexus has a routes feature that does something equivalent.
As already pointed out elsewhere on this site, see this page: Auto-Dependency Generation In short, gcc can automatically create .d dependency files for you, which are mini makefile fragments containing the dependencies of the .c file you compiled. Every time you change the .c file and compile it, the .d file will be updated. Besides … Read more
Easy. Here is the example from the top of my head: The top level CMakeLists.txt: cmake_minimum_required(VERSION 2.8.10) # You can tweak some common (for all subprojects) stuff here. For example: set(CMAKE_DISABLE_IN_SOURCE_BUILD ON) set(CMAKE_DISABLE_SOURCE_CHANGES ON) if (“${CMAKE_SOURCE_DIR}” STREQUAL “${CMAKE_BINARY_DIR}”) message(SEND_ERROR “In-source builds are not allowed.”) endif () set(CMAKE_VERBOSE_MAKEFILE ON) set(CMAKE_COLOR_MAKEFILE ON) # Remove ‘lib’ prefix for … Read more
While it won’t reveal unneeded include files, Visual studio has a setting /showIncludes (right click on a .cpp file, Properties->C/C++->Advanced) that will output a tree of all included files at compile time. This can help in identifying files that shouldn’t need to be included. You can also take a look at the pimpl idiom to … Read more