OFB Community Mailing Lists

The following archives are provided as a public service to the community. Opinions archived here do not necessarily represent the opinions of Open for Business or its contributors.

[CS-FSLUG] struggeling with cvs

Robert Wohlfarth rbwohlfarth at gmail.com
Wed Aug 12 20:29:07 CDT 2009


On Wed, Aug 12, 2009 at 6:33 PM, David McGlone <david at dmcentral.net> wrote:

> For one, I am wondering how changes are applied to a "final copy" for
> instance,
> say I have a repository with index.php in it and I have a working folder
> that
> I have checked out index.php to, Ok now supposed I change the copy of
> index.php in my "working" folder, I then comment the changes to the
> repository, the changes go into a file called "index.php,v" but I cannot
> for
> the life of me figure out how to apply the changes of the "index.php,v"  to
> the
> "index.php" file in the repository.
>

It sounds like three directories will work:
1) Repository
2) Working directory for development
3) Working directory for releases

You would...
1) Check out the repository to the development working directory.
2) Make code changes in the development working directory.
3) Commit changes to the repository.
4) Check out the repository to the release working directory.
5) Upload files from the release directory.

This seems a little weird for a one person setup. Think of it more in a
company setting. The people who make code changes (developers) do not
deliver them (release specialists). The developers commit to the repository
as work finishes. The release guys pull from the repository on a regular
schedule - like every 6 months.


> My biggest problem is it doesn't make sense to upload the copy you are
> working
> on, it makes sense to upload the copy in cvs, but it seems impossible.
>

CVS stores the initial copy in index.php. The index.php,v file holds all of
the changes made since that initial version. The CVS "checkout" command
automatically applies all of the changes for you.

It's easier to do everything from a working directory. Then you don't need
to muck with that behind-the-scenes processing. Having two working
directories separates the development code from the release version until
you're ready.

Hope that helps.

-- 
Robert Wohlfarth
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ofb.biz/pipermail/christiansource_ofb.biz/attachments/20090812/20813705/attachment.html>


More information about the Christiansource mailing list
Home About Connect: Twitter Facebook RSS
© 2001-2011 Universal Networks, All Rights Reserved. Some content rights may be held by Universal Networks' providers and used under license. Powered by ServerForest and SAFARI. Learn about our privacy policy here.