Bug 65680 – net-misc/clocksd-0.25.ebuild (New Package) - daemontools run-scripts for Dan Bernstein's clockspeed utilities

• Status: RESOLVED WONTFIX
• Product: Gentoo Linux

[Description Rodrigo Severo 2004-09-28 07:53:32 UTC]

Hi,


I'm including here clocksd-0.25.ebuild, 2 patchs and a helper startup script.

clocksd is a collection of daemontools run-scripts for Dan Bernstein's clockspeed utilities. clockspeed can synchronize your machine clock to subsecond precision with a reference clock via internet. clocksd just make this little magic really happens as most people don't now how to (or are too lazy to, this is me!) effectivelly make clockspeed work.

I suggest net-misc/clocksd.


Rodrigo Severo

[Comment 1 Rodrigo Severo 2004-09-28 07:55:29 UTC]

Created attachment 40619 [details]
clocksd-0.25.ebuild

[Comment 2 Rodrigo Severo 2004-09-28 07:56:47 UTC]

Created attachment 40620 [details, diff]
Patch for (hopefully) complete gentoonization of this package

[Comment 3 Rodrigo Severo 2004-09-28 07:57:21 UTC]

Created attachment 40621 [details, diff]
A conditional patch used by this ebuild

[Comment 4 Rodrigo Severo 2004-09-28 07:58:32 UTC]

Created attachment 40622 [details]
The helper startup script mentioned in this ebuild

[Comment 5 Rodrigo Severo 2004-09-28 08:03:08 UTC]

Just in case nobody finds any other bugs in this ebuild, I already now about one:

The last einfo on pkg_postinst() asks the user to run ${FILESDIR}/clocksd.startup.

I used ${FILESDIR} because 'man 5 ebuild' says: FILESDIR = "${PORTDIR}/${CATEGORY}/${PN}/files".

When I run this ebuild I get "/var/tmp/portage-pkg/clocksd-0.25/inf/files/clocksd.startup" and not the expected ""/usr/portage/net-misc/clocksd/files/clocksd.startup". Why?

Am I doing something wrong?


Rodrigo Severo

[Comment 6 Rodrigo Severo 2004-09-28 11:48:40 UTC]

Created attachment 40646 [details, diff]
A correction and an enhancement

I'm sending here a correction and an enhancement for this ebuild:

in clocksd-0.25.ebuild I including proper unmerge mesures and

in clocksd.startup I made it a little stronger in face of eventual adversities
during clock synchronization.


Rodrigo Severo

[Comment 7 Rodrigo Severo 2004-10-16 04:45:40 UTC]

Bump...

Well, this is mainly a bump message (has this bug been forgotten? :) but I would like to use it also to inform that this ebuild has been used successfully in 9 machines (servers and workstations) since, well, since the opening of this bug - 2004-09-28 - with no problems so far.

Is there anything else I could do to further help deployment of this ebuild? Please let me know.

[Comment 8 Rodrigo Severo 2004-10-29 12:27:31 UTC]

Created attachment 42868 [details]
clocksd-0.25.ebuild (Improved)

I made a few improvements to the ebuild (less manual work for the user). Main
functionality unchanged.

[Comment 9 Rodrigo Severo 2004-10-29 12:36:13 UTC]

Created attachment 42869 [details]
clocksd.startup (Improved)

The improved version of the startup script. It starts the svscan daemon by
itself.

[Comment 10 Thilo Bangert (RETIRED) (RETIRED) 2006-07-24 12:01:34 UTC]

hhm, upstream appears dead?!
the provided URL is no longer working anyway...

so, the clocksd package is basically a bunch of supervise style runscripts for clockspeed... ?

looks OK to me.

[Comment 11 Thilo Bangert (RETIRED) (RETIRED) 2006-10-19 03:09:32 UTC]

take a look at the clockspeed-conf package. if i am not mistaken it does the same thing and is already available in portage.

with a dead upstream this is unlikely to ever hit portage. closing for now.

nevertheless - thanks for your work. i feel ashamed that it "goes to waste" like this. keep it up.
kind regards
bangert