Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2012-04

Re: other replies to "Development of other revision control"

4 messages · 4 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Dawson
On 12/04/12 Reinier wrote 9 lines
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 5 lines
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)

Reply by email

Juha Manninen
to Dawson
Dawson wrote 8 lines
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.)

It worked for me on Linux when I was improving it. I used it for committing my changes then. (Otherwise I use git-svn link). I have understood other people are using it, too.

Juha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120414/acacd8a0/attachment-0001.html>

Reply by email

Reinier Olislagers
to Dawson: Yes, Rienier, that is kind of how I was thinking about it. I like neat solutions whenever…
Dawson wrote 20 lines
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".

Ok

> Then again, it's not my decision. Sorry for the foolish sounding question, but who would make this kind of decision?

I think the clich? is true: there are no foolish questions, only foolish answers... so trying not to make a fool of myself: If you're going to write the code, it'll be your decision. After it's done, and you've uploaded your patch to the bug tracker, it'll be the Lazarus core developers (the guys with commit rights on the SVN repositories) decision on whether or not to commit the revised component source code.
If you're touching FPC source code, same, but for FPC committers (they probably have quite some overlap with the Lazarus committers).

I think you're already well on your way to avoid surprises at the commit stage by getting people's opinion here.

Show quoted text 7 lines
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.)

Sorry, no, I don't have a (spare/any) SVN server handy and a bit too busy with database stuff right now...

Regards,
Reinier

Reply by email

Graeme Geldenhuys
to Dawson: Yes, Rienier, that is kind of how I was thinking about it. I like neat solutions whenever…
Dawson wrote
> Sorry for the foolish sounding question, but who would make this kind of decision?

Normally the person that implements it - but this is not always a guarantee either.

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

I had the same experience the last time I was
very good at crashing though. And now that I switched to git I need more fine grained commit control too. eg: I never commit whole files because I often code for a hour or so making lots of changes, then break my changes into lots of small atomic commits (committing a few lines of code here and there in a unit, until all changes in that unit are committed). Not even many GUI git frontends can do this, but git command line client and the git-gui (included with git can) - and this is vital to me and my workflow.

But I guess SCM + IDE integration is maybe meant for the simpler folk, thus whole file commits will be okay in their case.

me. There seems to be no mechanism for username / password challenging,

Username and passwords are so old-school. ;-) Can't SVN use a SSH or GPG or DSA key pair to do the validation?

Regards, ? - Graeme - _______________________________________________ fpGUI - a cross-platform Free Pascal GUI toolkit http://fpgui.sourceforge.net

Reply by email