Re: Updated squid 2.3 stable 3 for cygwin

cvs commit

it only saves changes to the files checked out, not any new files.

If you have created a new file which you also wants to have version
controlled, then you must add it to the branch with

cvs add filename

and then run "cvs commit" to save the file.

A recommendation is to build in a separate directory if possible
(requires GNU make or another make understanding VPATH). This way it is
more obvious what files have been created and possibly needs to be added
with cvs add as CVS prints out the names of "unknown" files it finds in
the source tree, and if you have built the binaries in the same
directory then a lot of "unknown" files are there making it hard to spot
those added source files you have forgot about.

How to: Run the configure script from the directory where you want to
build the binary. I.e. if you have /source/squid-cygwin, from any other
directory created for the build, run "/source/squid-cygwin/configure
--prefix=...", then make and so on as usual.

To clean up the source tree you can run "make distclean".

Yes, I'd prefer if code or coding related discussions are at least Cc:
to squid-dev@squid-cache.org, including CVS related issues.

/Henrik

Robert Collins wrote:
>
> Re: Updated squid 2.3 stable 3 for cygwinHenrik,
> I'm still reading some CVS how-tos, but I have a set of minimilistic
> working code for the cygwin branch. Is there an command that will update the
> branch, with my changed files, but not upload the intermediate targets?
> (If you'd prefer that this type of question always goes to the list, just
> tell me)
>
> Thanks,
> Rob
>
> ----- Original Message -----
> From: Henrik Nordstrom
> To: Robert Collins
> Cc: squid-dev@squid-cache.org
> Sent: Tuesday, July 04, 2000 9:08 AM
> Subject: Re: Updated squid 2.3 stable 3 for cygwin
>
> Robert Collins wrote:
> >
> > Thanks, I presume the branch was split off 2.4dev?
> Yes, only that I would not say it is split off from it. Based on
> 2.4.DEVEL is a better wording in this context, as the branch point is a
> moving target and not a static revision.
> CVS can make life a lot easier when used properly according to the
> context. The only apparent thing missing in the construct used for the
> Squid CVS repository on SourceForge is easy access to the history where
> changes has been propagated in the branch tree, but this is really a
> minor issue. All who need access to the current Squid sources for their
> modifications/extensions have it, and that is the most important thing.
> Note: The context of the SourceForge Squid CVS repository is to maintain
> modifications/extensions to Squid until committed into the main Squid
> release, not to maintain modified Squid versions.
> /Henrik
Received on Wed Jul 05 2000 - 00:33:12 MDT