my main worry

[Dean Hiller <dh...@avaya.com>]

My main worry is that you will never be able to have a project version map.  That is something that is quite complicated and if you are planning on tacking it on later, have fun.  I wish I had known about your project earlier so I could have mentioned it as a feature then.  thanks for the info.

ps why C instead of Java or C++?
Dean

Karl Fogel wrote:

> Hi, Dean.  It looks like your goals are only somewhat related to
> Subversion's (for example, we are not a build management system).
>
> If you'd like to see some of your features incorporated into
> Subversion, it would probably be best to hang around on the dev list,
> get a sense of what we're trying to do here, and then offer
> suggestions one digestible chunk at a time :-).  A wholesale merge is
> unlikely because the implications are not comprehensible in advance.
>
> Our code is in C; check out a working copy to see more.
>
> Best,
> -Karl
>
> Dean Hiller <dh...@avaya.com> writes:
> > Hello all,
> >     I have been developing my own source control system and just foud out about subversion today.  My system still seems quite orthogonal to yours believe it or not.  I would like to see one of two things happen.....(if possible)
> > 1.  see these features eventually in subversion
> > 2.  somehow combine projects(this is no small task seeing how orthogonal the two SCM's are)
> >
> > The main feature I would like to see is a viewable build map(attached is the concept I am centering the system around).  This could be side by side with a file version map.  Each node on the file version map maps to 1 or many nodes on the build map.  To see how much more orthogonal my system is(and some of the other radical ideas), go to  the following website
> >
> > http://sourceforge.net/docman/display_doc.php?docid=9859&group_id=46703
> >
> > Is there any interest?  Of course, I did not see anywhere on the website what language your code is in?  Is it in Java?
> >
> > Please reply directly to me also as I don't know if I successfully subscribed to the list.
> >
> > thanks for listening,
> > Dean
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: dev-help@subversion.tigris.org

Re: my main worry

[Dean Hiller <dh...@avaya.com>]

greg, thanks for the good explanation of "why C"
Mark, thanks for the tip, I will be following the project.

Karl and ALL,
    I have attached what a project map would look like(a gif file).  As 
you can see, it is not a linear thing.  No source control system 
anywhere has a project map.  Clearcase has file versioning maps on a per 
file basis.  This confuses the hell out of my developers because they 
think it is a project map like this is.  If you are linear, you will 
have a bitch supporting it unless it is built in early on.
Dean

Karl Fogel wrote:

>Dean Hiller <dh...@avaya.com> writes:
>
>>My main worry is that you will never be able to have a project
>>version map.  That is something that is quite complicated and if you
>>are planning on tacking it on later, have fun.  I wish I had known
>>about your project earlier so I could have mentioned it as a feature
>>then.  thanks for the info.
>>
>
>What is a project version map, and what is required to support one?
>

Re: my main worry

[Karl Fogel <kf...@newton.ch.collab.net>]

Dean Hiller <dh...@avaya.com> writes:
> My main worry is that you will never be able to have a project
> version map.  That is something that is quite complicated and if you
> are planning on tacking it on later, have fun.  I wish I had known
> about your project earlier so I could have mentioned it as a feature
> then.  thanks for the info.

What is a project version map, and what is required to support one?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: my main worry

[Greg Stein <gs...@lyra.org>]

On Fri, May 17, 2002 at 05:41:10PM -0400, Dean Hiller wrote:
>...
> ps why C instead of Java or C++?

Why not? Your question implies that choosing C instead of the others was a
poor choice. :-)

We chose C for a number of reasons:

- more people know C and are willing to contribute to C-based applications;
  the theory here being that we could have a larger community of
  contributors than if we had chosen Lisp, Python, C++, or Java (all of
  these were considered at various points in time)

- C libraries can be called from *everything*; it is much more difficult to
  call a Java library from Perl (while a C library from Perl or Java is
  quite easy).

- it was the best common denominator between the original set of coders (and
  remains so)

etc etc, that I haven't thought of, offhand.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org