On 2024-01-15 11:15:32 -0500, Theodore Ts'o wrote: > For example, when I implemented libuuid, if you want to create a huge > number of UUID's very quickly, because you're a large enterprise > resource planning application, the the uuidd daemon will allow > multiple processes to request "chunks" of UUID space, and create > unique UUID's without having to having to go through some kind of > locking protocol using a single shared state file. > > So libuuid works just fine without uuidd, but if you are populating a > large ERP system, then you very much will want uuidd to be installed. > So in that case, you can make the dependency relationship be either > suggests or recommends, instead of a hard dependency.
Except that in Debian, this is a "Recommends:", and "Recommends:" are normally installed by default... except by the Debian installer! This is inconsistent. So, in the present case, uuid-runtime wasn't installed by default, though libuuid1 was installed and had a "Recommends: uuid-runtime". But with the 64-bit time_t transition, libuuid1 got replaced by libuuid1t64 a few days ago, which pulled uuid-runtime. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
