So it took me a little longer than I had originally planned, but there were a few minor problems to be fixed/tested before doing a new release. In any event the version of collectl on sourceforge now has the new directory tree structure which can either be used as-is with debian or if some additional tweaking is required it should be fairly minimal, I hope. If anything more needs to be tweaked on my end just let me know... -mark
>-----Original Message----- >From: Bernd Schubert [mailto:[email protected]] >Sent: Monday, December 14, 2009 10:31 AM >To: Seger, Mark >Cc: Tim Retout; [email protected] >Subject: Re: RFS: collectl > >On Monday 14 December 2009, Seger, Mark wrote: >> >-----Original Message----- >> >From: Tim Retout [mailto:[email protected]] >> >Sent: Monday, December 14, 2009 10:20 AM > >> >You don't have to get rid of them necessarily, if they're useful >> >documentation. >> > >> >> - is it ok to keep my utility scripts in /usr/share/collectl/util >so >> >> - I don't corrupt /usr/bin with files nobody really ever uses? The >> >> - man pages I wrote for them DO include the explicit path so people >> >> - will know how to find them if they really want to. >> > >> >That's probably best, because otherwise we *will* need man pages. :) >> > >> >So I'd just make a release, and then you can make another release if >> >we come back with a huge set of man page fixes or whatever. >> >> great. In that I'm going to remove the manpages since I don't really >thing >> they add any value and the utilities to have a 'usage' output when >you run >> them w/o switches. I think it also will help keep things simpler. >> >> So should I just consider the kit done then and upload it to >sourgeforge >> as-is? > >Yes, please. I will then create a new package later on. > > >Thanks, >Bernd -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
