[Lazarus] Re: other replies to "Development of other revision control"

[Dawson]

On 12/04/12 Reinier wrote:

> I'd rather have a single package that supports multiple systems - if
> necessary with extensions for certain systems (e.g. things that git can
> do that SVN can't).
> This package would talk to various revision control system classes
> (using an API/interface/factory model, however you want to call
> it/implement it).
> The project directory could contain a file (or perhaps an extension to
> the .lpi file, don't know if that is allowed) that specifies which RCS
> to use, as well as URLs, usernames, perhaps passwords etc.

Yes, Rienier, that is kind of how I was thinking about it. I like neat
solutions whenever possible. The code is generally easier to write and
maintain. (as I said in an earlier post, any information needed for
doing SCM transactions would be negotiated by a user controlled
interface (configurations). Some configuration information, such as what
type of SCM mechanism is being used, and presets for which files to
ignore etc could be stored on a project by project basis either in the
.lpi, or somewhere in the project folder, for instance "scmSettings.cfg".
> Then again, it's not my decision.
> 
Sorry for the foolish sounding question, but who would make this kind of
decision?

Ludo wrote:

> I completely agree. The only assistance I would expect when adding a file to
> a project is to pre-check the box in front of the filename in the commit
> window. Just to avoid searching in a list of sometimes hundreds of
> un-versioned files. If it is pre-checked it is much easier to find.
> 

me too! I would want the user to have full control over what
transactions are to take place. I also would want to have as much
feedback from the transactions as possible. For example as it is right
now I am completely unable to get lazsvnpkg to do anything useful for
me. There seems to be no mechanism for username / password challenging,
maybe that is my problem? The repository I use requires me to give login
credentials. (I am aware that there are a number of protocols for SVN.)

Thanks Ludo!

Can anyone tell me how to use lazsvnpkg? I get all the forms popping up
the way they should based on menu clicks, but I can't get it to do much
more than crash. I have been using the command line tools since I
couldn't get lazsvnpkg to work for me. (I could explore the code, which
I plan to do anyway, but if anyone has any pointers, I'd be happy to
explore them. I couldn't find any description of what to do, and sorry,
it is not obvious to me what I need to do to get it to work.)

Dawson (aka abudeveloper)