hey guys , what about a CVS server ? - Minix

This is a discussion on hey guys , what about a CVS server ? - Minix ; hi , What about a CVS server at www.minix3.org site ? in which you can browse the source code ? thanks , Richard Karcher...

+ Reply to Thread
Results 1 to 11 of 11

Thread: hey guys , what about a CVS server ?

  1. hey guys , what about a CVS server ?

    hi ,

    What about a CVS server at www.minix3.org site ? in which you can
    browse the source code ?

    thanks ,

    Richard Karcher


  2. Re: hey guys , what about a CVS server ?

    If we are going to set up version control my vote is for subversion,
    not CVS


  3. Re: hey guys , what about a CVS server ?

    My vote also is for subversion.


  4. Re: hey guys , what about a CVS server ?

    Karram wrote:
    > My vote also is for subversion.
    >

    Why subversion? Why not CVS? My vote is on CVS.

  5. Re: hey guys , what about a CVS server ?

    yeah, a repository would be very nice to see what's being worked on and
    so other people can fix bugs etc

    prefer subversion though, check http://subversion.tigris.org/ if you
    want to know why


  6. Re: hey guys , what about a CVS server ?

    Some advantages of SVN over CVS are
    1) Atomic checkins : If something goes wrong during a checkin, a CVS
    repository can be in an unstable state. SVN does not let this happen.
    2) SVN makes it easier to branch and tag than CVS.
    3) It can be run over apache.


  7. Re: hey guys , what about a CVS server ?

    Some more advantages:

    It's possible to move files in subversion, which you cannot do in CVS
    without deleting and then adding the file (which sucks because then you
    lose versioning history)

    CVS is built on a lot of legacy stuff like RCS, whereas subversion
    doesn't carry a lot of the same historical baggage.

    Subversion supports binary diffs, CVS does not

    In subversion, commit and update speeds are based on size of changes.
    In CVS, those speeds are based on the size of the file being changed.


  8. Re: hey guys , what about a CVS server ?

    I think if subersion (which I have never used, I have however used CVS,
    SCCS, and RCS) were going to be used for Minix source browsing, it would
    make sense to first have subversion running on Minix. Is someone porting
    it? I like to have the tool on the machine I do development on. Currently,
    Minix supports CVS and RCS.

    The Grue

    wrote in message
    news:1135640177.170007.116190@g43g2000cwa.googlegr oups.com...
    > Some more advantages:
    >
    > It's possible to move files in subversion, which you cannot do in CVS
    > without deleting and then adding the file (which sucks because then you
    > lose versioning history)
    >
    > CVS is built on a lot of legacy stuff like RCS, whereas subversion
    > doesn't carry a lot of the same historical baggage.
    >
    > Subversion supports binary diffs, CVS does not
    >
    > In subversion, commit and update speeds are based on size of changes.
    > In CVS, those speeds are based on the size of the file being changed.
    >




  9. Re: hey guys , what about a CVS server ?

    Grue:

    I disagree, I think it makes less sense to get subversion running on
    minix first. Version control and bug tracking are 2 systems that we
    should not mess with,especially since we are using it for production.
    Stability is by far the most important factor for those 2 systems. If
    we are going to use version control or any other critical collaboration
    tools, I strongly suggest we go with some tried and true solution like
    linux+apache+subversion. That will take the least amount of time to
    setup, give us top notch collaboration tools, and we will have some
    assurances that the tools we want to use are much less likely to get
    hosed, provided we run a common configuration for the platform.


  10. Re: hey guys , what about a CVS server ?

    I think maybe you misunderstood me. I meant that since I am developing for
    Minix, doesn't it make sense for me to have my software control system run
    under the OS I will do the work on. I did not mean for the repository to
    reside on Minix, I just meant that it would be nice for me to be able to
    fire up my Minix machine, pull down the latest files and get
    coding/testing/debugging what is there. If you use a tool that isn't
    supported on Minix, you add the step of having to move the files to a Minix
    system to code/build/run and checking them back in would also require moving
    it back to a system that runs subversion/apache. Then you run the risk of
    people using Windows machines and transferring code wrong and checking in
    files with the wrong crlf. Makes a mess. Of course, maybe subversion
    handles all that internally, like I said before, I have never used it. I am
    by no means against it, I just like my tools on the machine I am doing the
    work on.

    The Grue

    wrote in message
    news:1135791782.367658.314910@f14g2000cwb.googlegr oups.com...
    > Grue:
    >
    > I disagree, I think it makes less sense to get subversion running on
    > minix first. Version control and bug tracking are 2 systems that we
    > should not mess with,especially since we are using it for production.
    > Stability is by far the most important factor for those 2 systems. If
    > we are going to use version control or any other critical collaboration
    > tools, I strongly suggest we go with some tried and true solution like
    > linux+apache+subversion. That will take the least amount of time to
    > setup, give us top notch collaboration tools, and we will have some
    > assurances that the tools we want to use are much less likely to get
    > hosed, provided we run a common configuration for the platform.
    >




  11. Re: hey guys , what about a CVS server ?

    Ah yes, miscommunication, I thought you meant we should serve the
    repository off of Minix. What are you saying is that the version system
    we use should have a client that can run locally on minix. I agree, it
    is dangerous to move files around by hand, should be developing
    directly from the working copy. As far as minix support for subversion
    client im not sure, but I can't imagine it would be too difficult to
    achieve, if it doesn't already work.

    the faq says it requires the apache portable runtime, so if that
    already works on minix it'll probably work fine:
    http://subversion.tigris.org/faq.html#portability

    thoughts?

    --Mike


+ Reply to Thread