Thus spake Ruslan Ermilov <[EMAIL PROTECTED]>: > On Thu, Jan 30, 2003 at 09:58:15PM -0800, David Schultz wrote: > > I don't know about Steve, but cvsup is the wrong answer for me > > because it's a mirroring tool and not a version control tool. > > Among the things I would like to do are: > > > > - Update to a specific version of a specific file from the > > repository. > > > > - Generate a diff between two revisions in the repository, > > or between a version in the repository and some local > > patches of my own. > > > > - View logs for particular files. > > > > I asked the question in hopes that there would be some neat > > feature of cvsup that mocked up some CVS metadata for me, but > > since nobody has mentioned any such thing, I guess I'm out of > > luck. Mirroring the entire repository is not an option on > > machines with less than 6 GB of spare disk.[1] Transferring the > > entire source tree over the network via anoncvs is suboptimal when > > all I really want is a few kilobytes of 'CVS' subdirectories. > > But I guess it will have to do for now. > > > > > > [1] When the system is an aging dual PPro or 200MHz Alpha using > > SCSI, buying new drives is not practical. > > > Well then learn how to use anoncvs?
I use anoncvs. My question was, given a source or ports tree without any CVS metadata, is there a way to obtain the tiny corresponding CVS/Entries and CVS/Repository files without checking out an entirely new copy of the tree via a busy, often overloaded, anoncvs server. Keep in mind that I'm not asking a ``can it be done?'' question. I've been doing it for years. Rather, I'm asking, ``can it be done more efficiently?'' So far, the best answer I've received is ``mirror the repository locally'' (thank you, David), which I already do on one machine to maintain a local branch and will consider doing on others. I have also considered writing a script to parse embedded $FreeBSD$ tags out of source files and mock up a CVS/Entries and CVS/Repository based on that information. Perhaps I will try that and see if it works passably well. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
