[TriLUG] Topic for discussion

[H. Wade Minter]

Oh, so you want to get software out of CVS, not set up a CVS repository
for your own use.  K.

Usually, getting and building software out of CVS is trickier to do than
using packages versions, because pulling from CVS gets you a snapshot in
time of the software's development - it's possible to get broken code
that way, and have it not build.  It's generally considered
"bleeding-edge".

For things like Wine, you can use:
http://www.winehq.org/download.shtml

to get daily builds, which would probably suit you better.  They're built
every day from CVS, so they're current, but they're in a more manageable
form.

However, if you want to pull source out of CVS and build it, you use the
"cvs" client commands available on Unix to do it.  For Wine, you'd follow
the instructions here:
http://www.winehq.org/dev.shtml

Basically, you log into the remote CVS server, then you "check out" the
software module that you want.  It then puts the source onto your local
system for building.

That help?  Need more details/etc.?

--Wade

On Thu, 18 Oct 2001, Vestal, Roy L. wrote:

> Thanks for the info. It sounds like a form of SCCS.
>
> I would like to know more of HOW to use it as an end user. For example, I
> want to start using WINE for a few projects, but I currently download RPM's
> (I'm running Mandrake and RH on my boxes) and on the newsgroups I get the
> impression that using the latest "CVS" is better, and if there is a change,
> it's easier to get the lastest "CVS" than to wait for someone to create an
> RPM.
>
> I don't understand HOW it works. I want to know that before I use something
> that "powerful".
>
> Any help is greatly appreciated.
>
> -----Original Message-----
> From: H. Wade Minter [mailto:minter at lunenburg.org]
> Sent: Thursday, October 18, 2001 4:02 PM
> To: 'Trilug-Triangle Linux Users Group'
> Subject: Re: [TriLUG] Topic for discussion
>
>
> It's a version control system (Concurrent Versioning System, IIRC).  There
> are several uses for it - I use it for two main things:
>
> 1) For version control on a software project I write.  CVS lets me track
> back through every change to every source code file, so I can remember
> what changed and when.  You can also use CVS to "tag" moments in time, so
> if I want to see how my project looked at version 0.9, I can get it back
> to that state exactly.
>
> 2) For a website I run, I have a development site and the live site.  I do
> all of my changes in the devel site, commit them to CVS, and then check
> them out in the live site.  It helps me test my changes, and lets me
> quickly roll back to a known-good state if I make a mistake.
>
> I'm not a CVS expert by any means, but I'd be glad to go into more detail
> if you want.
>
> --Wade
>
>
> On Thu, 18 Oct 2001, Vestal, Roy L. wrote:
>
> > I'm new to the CVS world.  Could someone explain what it is, and how it
> > works?
> >
> > _______________________________________________
> > TriLUG mailing list
> > http://www.trilug.org/mailman/listinfo/trilug
> >
>
> --
> Do your part in the fight against injustice.
> Free Dmitry Sklyarov!  http://www.freesklyarov.org/
> Fight the DMCA!  http://www.anti-dmca.org/
> STOP the SSSCA! http://www.eff.org/alerts/20010921_eff_sssca_alert.html
>
> _______________________________________________
> TriLUG mailing list
> http://www.trilug.org/mailman/listinfo/trilug
> _______________________________________________
> TriLUG mailing list
> http://www.trilug.org/mailman/listinfo/trilug
>

-- 
Do your part in the fight against injustice.
Free Dmitry Sklyarov!  http://www.freesklyarov.org/
Fight the DMCA!  http://www.anti-dmca.org/
STOP the SSSCA! http://www.eff.org/alerts/20010921_eff_sssca_alert.html