Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!munnari!otc!metro!basser!john From: john@basser.oz (John Mackin) Newsgroups: news.admin,comp.sources.d Subject: Re: readership measurement, arbitron, sources, etc. Message-ID: <1114@basser.oz> Date: Tue, 3-Nov-87 06:37:41 EST Article-I.D.: basser.1114 Posted: Tue Nov 3 06:37:41 1987 Date-Received: Sat, 7-Nov-87 09:35:45 EST References: <107@bacchus.DEC.COM> <166@uwspan.UUCP> Reply-To: john@basser.oz (John Mackin) Followup-To: news.admin Organization: Dept of Comp Sci, Uni of Sydney, Australia Lines: 31 Summary: not hard to keep up-to-date Xref: mnetor news.admin:1336 comp.sources.d:1524 In article <166@uwspan.UUCP> root@uwspan.UUCP (John Plocher) writes: > If you > post a copy monthly to a discussion group, how will I know if it is another > copy of the one I have, or if it is a NEW version? [...] If I > need to look at it every month to make sure I have the latest version, I > can't/won't have the time. By conincidence, John's article arrived here hard on the heels of Brian's most recent posting of arbitron. Hence, I was moved to respond. In fact, it is no trouble at all, at least for me. arbitron is very stable; Brian hasn't changed it in six months. All that happens is, the posting arrives, I see that it is still version 2.4.2, I think `yep! still the same', and blithely ignore it. So keeping up to date isn't much hassle. And anyway, try this: when you hack the distributed arbitron so it works fine on your system, just take a context diff of the original against your version, and save it in a file in your news library directory, along with arbitron (say, "arb.pat"). Then when a new arbitron version DOES come along, just patch