Re: [microblaze-uclinux] Petalinux and CVS

["David H. Lynch Jr." <dhlii@xxxxxxxxxxx>]

    I am only loosely using PetaLinux. Basically I borrow the PetaLinux
and uClinux patches and integrate them into my own
Linux source tree.

    I would recommend against CVS.  New projects are not using it, Linux
kernel projects are not using it.

    Most Linux kernel work uses GIT. Git is significantly different,
from traditional server based SCM's.
    It is a distributed SCM. I am still having alot of trouble trying to
wrap my head arround git and the
    fundimental concepts needed to use it most effectively. That said it
takes very little effort to understand
    enough of the basics to do all the tasks that you are used to with CVS.
    But grasping how to effectively use all the branch merge options,
how to sync a single local git repository
    against numerous different remote ones, how to efficiently use git
to put together clean properly formated patches
    as they are expected for kernel submission. Those kind of tasks -
things you really can not do in CVS are
    taking some time to really grasp.
    Regardless, git is an excellent fast, very powerful SCM. It is the
SCM for linux kernel work. It has been seriously considered for
    many very large Open Source projects. Its major failing at the
moment is poor support for Windows.

    The next "big" alternative is Subversion. Subversion is probably the
most popular SCM outside the Linux Kernel.
    It has all the features of CVS, it is comfortable for CVS users to
move to, but it is much cleaner than CVS.
    Subversion was not intended to be the best SCM in existance. But it
is intended to replace CVS.
    Subversion has pretty much all the cross platform support CVS has
and probably more.
   
    Additionally, there is svk - which is a subversion like SCM that is
actually built on top of subversion.
    svk adds offline functionality, eliminates all the metadata from
your working copy/sandbox and adds
    some of the distributed capabilities of things like git, while
maintaining the friendlyness of subversion.
    svk uses subversion repositories, so you can use either svn or svk
as a client.
    In general svk is a better choice than svn if you do alot of
disconnected work or if you frequently access
    a subversion repository over the internet.

    There are a plethora of other good choices after that. But in the
long run I expect most of the other choices to fade.
    git's extensive use by kernel developers will assure that whatever
arguable advantages other distributed SCM's might have
    those of actual value will be incorporated into git. git will
eventually get the windows support and UI integration that
    subversion has and may pose a very credible challenge to subversion
as a general purpose SCM. Though some of its speed and
    power come at a cost in complexity.

    I think most SCM's include the ability to to ignore files by name,
type or pattern.
   







Rod Campbell wrote:
> We have been using uClinux for a year or so.  We manage the sources on
> CVS.  
>
> I just downloaded Petalinux to give it a try, and the first thing I
> wanted to do was place it on CVS to keep track of any changes I make.  I
> want to do a correct cvs import.  For uClinux, one could use cvs import
> -ko -I ! -m "xxxxx" aaaa bbbb cccc.  This works because uClinux does not
> (as far as I know) have any binary files in the distribution.   
>
> There are binary files in several places in the Petalinux directory
> structure, many of them without any kind of file extension (*.o, *.a,
> *.elf - etc.), so it appears to me that a .cvswrappers file is not
> enough to use as guidance for when to use -kb for a file.  Has anyone
> come up with a method for doing this?  Is there a consistent naming
> convention for the directories that contain binary files?.
>
> For those of you that are using Petalinux now, what source code
> versioning system are you using to deal with this?
>
> Thanks.
>
>   

___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/