28ac782583
There are many more packages to fix, this is just a start. Rules: * Don't repeat the package name (not always that easy...) * Start with capital letter * Don't end with full stop * Don't start with "The ..." or "A ..." I've also added descriptions to some packages and rewritten others.
27 lines
1.3 KiB
Nix
27 lines
1.3 KiB
Nix
{ stdenv, fetchurl, libcap, readline }:
|
||
|
||
assert stdenv.isLinux -> libcap != null;
|
||
|
||
stdenv.mkDerivation rec {
|
||
name = "chrony-1.27";
|
||
|
||
src = fetchurl {
|
||
url = "http://download.tuxfamily.org/chrony/${name}.tar.gz";
|
||
sha256 = "17dfhcm5mrkg8ids0ajwscryr7fm7664kz10ygsa1ac047p3aj6l";
|
||
};
|
||
|
||
buildInputs = [ readline ] ++ stdenv.lib.optional stdenv.isLinux libcap;
|
||
|
||
meta = with stdenv.lib; {
|
||
description = "Sets your computer's clock from time servers on the Net";
|
||
homepage = "http://chrony.tuxfamily.org/";
|
||
license = licenses.gpl2;
|
||
platforms = platforms.unix;
|
||
|
||
longDescription = ''
|
||
Chronyd is a daemon which runs in background on the system. It obtains measurements via the network of the system clock’s offset relative to time servers on other systems and adjusts the system time accordingly. For isolated systems, the user can periodically enter the correct time by hand (using Chronyc). In either case, Chronyd determines the rate at which the computer gains or loses time, and compensates for this. Chronyd implements the NTP protocol and can act as either a client or a server.
|
||
|
||
Chronyc provides a user interface to Chronyd for monitoring its performance and configuring various settings. It can do so while running on the same computer as the Chronyd instance it is controlling or a different computer.
|
||
'';
|
||
};
|
||
}
|