On Thu, 2002-08-15 at 08:41, David Eastcott wrote: > On Thursday 15 August 2002 11:27 am, you wrote: > > On torsdagen den 15 augusti 2002 05.09 Tibor Pittich wrote: > > > On 15. aug 2002 00:59, Oden Eriksson wrote: > > > > I have updated the ntp package, either use attached patch, get the > > > > package at http://d-srv.com/Cooker/, or ignore the whole thing... > > > > > > it is possible to split this package into two(?) parts? ntp-server, > > > ntp-clients.. > > On those nachines not wanting to be a server, would it not just be a matter > of chkconfig --del ntpd?
Of course you could, but why have servers installed on a system if your never going to use them? (think of all the morons out there who are running "default" installs of other distros where every server and service is turned on by default) This my friends is called BLOAT. Not that I think we need MORE packages, but I think it's the lesser of two evils. > > > > > > > many machines is synced via ntp protocol, but not all want be a ntp > > > server;) > > > > Excellent idea! > > > > I'll try to fix it and hope it will be accepted. > > Be kinda interesting to know how you propose to split package? you could use the same src rpm tree, but create two packages, you build the whole thing, but at the end of build you run a script that: For client.rpm - only "make installs" the client binary and config files for server.rpm - "make installs" server and server config files. For anything common that they both require, I'd suggest you include it in the client.rpm and have the server.rpm REQUIRE the client rpm, alternatively you could create a THIRD package with ntp-common but I'd recommend against that, there are to many damn packages to keep track of as it is... just my two cents... Ryan
