I've never envisioned update-setup as a product. I don't want to be in the position of maintaining YA package.
You have a copy of the program and you can update it as you see fit. I don't think it's necessary to make it generally available and, in fact, it *isn't* generally available. So, grab it, hack on it, share it with your friends. I don't care. I am just not interested in bug reports on it right now. cgf On Fri, Oct 05, 2001 at 10:16:23AM -0400, Jason Tishler wrote: >Chris, > >[Sorry, for chiming in late, but I have been on vacation for the last 5 >days.] > >On Tue, Oct 02, 2001 at 05:36:34PM -0400, Christopher Faylor wrote: >> I'm not going to guarantee that update-setup is around for the long haul. >> That's one reason why it is not publicly available. > >I have found it very useful to be able to generate "private" setup.ini >files via update-setup. For example: > > update-setup /misc/cygwin jt > >splices a "jt" branch onto my local Cygwin mirror. > >Do you envision any way to accomplish this, when (and if) update-setup >meets its demise? Note that I'm quite willing to do the work -- I'm just >trying to make sure that the necessary hooks are in place in whatever >will be generating setup.ini going forward. > >Thanks, >Jason -- [EMAIL PROTECTED] Red Hat, Inc. http://sources.redhat.com/ http://www.redhat.com/