info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: branches off of branches


From: Kaz Kylheku
Subject: Re: branches off of branches
Date: Thu, 19 Jun 2003 14:11:28 -0700 (PDT)

On Thu, 19 Jun 2003, Peschko, Edward wrote:

> but it then behooves you to remember when you've done 
> the damn merge..
> 
> Argh! Overall, cvs's branching ability leaves much to be desired. 
> I'd use MetaCVS, except I need to have the functionality available 
> on solaris....

What issues have you run into trying to get Meta-CVS on Solaris?

There exists a website ``www.solaris4u.dk'' which hosts categorized
lists of software that apparently run on Solaris. Meta-CVS and other
version control systems are stuck under the ``search engines''
category.

  http://www.solaris4you.dk/searchenginesSS.html

The table suggests that the program was at least built on Solaris 2.8
and 2.9, SPARC and X86.  Maybe the site's maintainer has binaries.

I don't use Solaris, but I'd be happy to incorporate patches, if any,
that are needed to get it running, and host the binary tarballs too.

> (ps - also wrt MetaCVS... why isn't there a sourceforge project for it?)

The conditions are not right.

So far, I have received very few patches for Meta-CVS. Every ChangeLog
entry has my name on it! So there isn't a development team that needs a
central repository.

Read-only repository access for the masses would make sense if it was
such a widely used, busy and buggy program that it was mandatory for
thousands of people to get the latest codebase several times a day
in hopes that the latest and greatest will solve their problems.

A mailing list would be needed for similar reasons. The
Meta-CVS-related traffic that I receive in my personal mailbox is so
small that it doesn't require its own list. The odd time two people
have the same ideas or problems, so I may put them in touch.

A better question is: why isn't there actual working source code for 90%
of the Sourceforge projects? :)





reply via email to

[Prev in Thread] Current Thread [Next in Thread]