atso

The manual is worth a read. This is a software (as gcc) in which the "man" page or the information displayed with "--help" is not near the bunch of things there are described in the complete documentation.

You have clang-tidy:

https://www.kdab.com/clang-tidy-part-1-modernize-source-code...

Could you post a link, please? Searching for those terms leads to a '96 book and some different blog posts, but I am not sure if the ones you are referring to. Thanks!

You can do `make -j4 install`. Works as intended.

Well, both the article and the video say that there is more than one factor for reaching stability, not only momentum.

I think that this is the current status, knowing that the bike does not fall by the simultaneous combination of several factors. When analyzing the problem mathematically, it can be found that there are additional stability factors that do not even have direct physical meaning.

Of course once the makefile is generated, there is no need to use cmake (as long as the project is not modified), but you cannot share a makefile generated by cmake, not even redistribute it. You cannot even re/locate it on your hard drive.

The difference is that autotools generates source distributions that do not need autotools to build, while a cmake project always requires cmake when building.

I hear about rdiff-backup, but I think its two main drawbacks are:

* on the webpage, there is no new release since 2009.

* has no de-duplication.

I was considering moving my 5+ years old rdiff-backup system to any of those new, promising programs:

* obnam [http://liw.fi/obnam/]

* attic [https://pythonhosted.org/Attic/]

They both do automatic de-duplication, old backup deletion and remote encryption.