Sign in Join

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

Mailing lists / lazarus / 2013-03

tiOPF: Repository migrated to Git

6 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

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

Graeme Geldenhuys

Hi,

In case there are anybody using tiOPF, please note the following. I'll also update the Free Pascal wiki in the next few minutes.

Earlier message 102 lines
-------- Original Message -------- Subject: Repository migrated to Git Date: Wed, 27 Feb 2013 19:43:33 +0000 From: Graeme Geldenhuys Newsgroups: tiopf.development,tiopf.support,tiopf.general Hi, As discussed some months ago, I have finally made the move. After various attempts, to see what is the best possible solution, I found something that works. Due to our very odd SubVersion repository layout, it made the migration rather difficult. Anyway, you can checkout the new repository as follows: git clone git://tiopf.git.sourceforge.net/gitroot/tiopf/tiopf This will create a 'tiopf' directory will the repository inside. Note: tiOPF users that have read-write access to SubVersion must use the following syntax to get read-write access to the Git repository: git clone ...replacing [username] with your SourceForge username. It will download +-19MB. You will then have the main tiOPF repository that contains 4 branches. master - contains nothing, but a readme file. This is equivalent to what Trunk (in SubVersion terms) would be. But that is just a guideline. Due to the nature of the migration, we will not be using this branch for development work. tiopf1 - Contains the tiOPF version 1 code. No history because there was none, when did the conversion from Team Coherence to SubVersion, many years back. tiopf2 - Contains the tiOPF version 2 code, with all its history. tiopf3 - Contains the tiOPF version 3 code, with all its history. Once you cloned the repository, git will leave you in the 'master' branch. To switch to another branch, simply run: git checkout <branch_name> eg: git checkout tiopf2 or git checkout tiopf3 I've also decided to split the old SubVersion repository into multiple Git repositories as follows: tiopf - the main source code repository, as described above tiopf_docs - the unit and class documentation tiopf_3rdparty - a snapshot of the latest code of the 3rdParty directory. I noticed that tiOPF3 also has a copy of this. I might remove that later. This will not be maintained, and hopefully later get phased out. Most of those components are rather out of date already. tiopf_apps - this will contain the support apps of tiOPF. Things like the tiSQLEditor, our old Mailing List software etc. tiopf_website - the HTML source for our website. tiopf_scripts - Build scripts (not 100% sure if this is still needed) At the moment I only have the 'tiopf' repository done. The others will follow in the next few days. I'll soon post a short message showing the basic usage of git, and a small typical workflow. There are 1000's of great articles and free eBooks on Git though. To get started with git, you only need about 5 git commands, and can learn the rest if and when needed. Many Windows users will probably opt for TortoiseGit, but that is not required, as the official Git install includes excellent command line and GUI tools as standard. The Windows installer also asks if you want Windows Shell integration for the GUI git tools. Git Downloads: http://git-scm.com/downloads Git Documentation, Tutorials and Videos: http://git-scm.com/doc ps: The SubVersion repository is still active. I'll ask SourceForge to mark it as read-only soon. Then after a few months, we can remove it completely. Regards, - Graeme - ----------------------[ end ]-------------------------

Reply by email

Frank Church
to Graeme Geldenhuys
Graeme Geldenhuys wrote 71 lines
Hi, In case there are anybody using tiOPF, please note the following. I'll also update the Free Pascal wiki in the next few minutes. -------- Original Message -------- Subject: Repository migrated to Git Date: Wed, 27 Feb 2013 19:43:33 +0000 From: Graeme Geldenhuys Newsgroups: tiopf.development,tiopf.support,tiopf.general Hi, As discussed some months ago, I have finally made the move. After various attempts, to see what is the best possible solution, I found something that works. Due to our very odd SubVersion repository layout, it made the migration rather difficult. Anyway, you can checkout the new repository as follows: git clone git://tiopf.git.sourceforge.net/gitroot/tiopf/tiopf This will create a 'tiopf' directory will the repository inside. Note: tiOPF users that have read-write access to SubVersion must use the following syntax to get read-write access to the Git repository: git clone ...replacing [username] with your SourceForge username. It will download +-19MB. You will then have the main tiOPF repository that contains 4 branches. master - contains nothing, but a readme file. This is equivalent to what Trunk (in SubVersion terms) would be. But that is just a guideline. Due to the nature of the migration, we will not be using this branch for development work. tiopf1 - Contains the tiOPF version 1 code. No history because there was none, when did the conversion from Team Coherence to SubVersion, many years back. tiopf2 - Contains the tiOPF version 2 code, with all its history. tiopf3 - Contains the tiOPF version 3 code, with all its history. Once you cloned the repository, git will leave you in the 'master' branch. To switch to another branch, simply run: git checkout <branch_name> eg: git checkout tiopf2 or git checkout tiopf3 SubVersion repository is still active. I'll ask SourceForge to mark it as read-only soon. Then after a few months, we can remove it completel -- _______________________________________________ Lazarus mailing list http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Which branch should I checkout to use with Lazarus? The information on the website is bit confusing. The tiopf2 branch appears to date back to 2008

Frank Church ======================= http://devblog.brahmancreations.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20130405/0885de61/attachment.html>

Reply by email

Graeme Geldenhuys
to Frank Church
Frank Church wrote
Which branch should I checkout to use with Lazarus?

tiOPF2 branch.

FPC still can't compile the tiOPF3 branch, due to Unicode and other Delphi language features. Feature wise, tiOPF2 and tiOPF3 are near identical, and I keep them in sync.

The information on the website is bit confusing.

The tiOPF website or the FPC/Lazarus wiki?

I just updated the FPC/Lazarus wiki page with the latest information.

http://wiki.lazarus.freepascal.org/tiOPF

The tiopf2 branch appears to date back to 2008

Uh? The latest commit was done today.

Regards,
- Graeme -

fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://fpgui.sourceforge.net/

Reply by email

Zaher Dirkey
to Graeme Geldenhuys

Why you hate "master", i believe it is for last working version, here is tiOPF3, i do that, and for me it have all fixes in it, so who need last of every thing he will take "master".

Graeme Geldenhuys wrote 39 lines
On 2013-04-05 18:03, Frank Church wrote: > > Which branch should I checkout to use with Lazarus? tiOPF2 branch. FPC still can't compile the tiOPF3 branch, due to Unicode and other Delphi language features. Feature wise, tiOPF2 and tiOPF3 are near identical, and I keep them in sync. > The information on the > website is bit confusing. The tiOPF website or the FPC/Lazarus wiki? I just updated the FPC/Lazarus wiki page with the latest information. http://wiki.lazarus.freepascal.org/tiOPF > The tiopf2 branch appears to date back to 2008 Uh? The latest commit was done today. Regards, - Graeme - -- fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://fpgui.sourceforge.net/ -- _______________________________________________ Lazarus mailing list http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
I am using last revision of Lazarus, FPC 2.6 on Windows XP SP3 Best Regards Zaher Dirkey -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20130406/3de2c9d4/attachment.html>

Reply by email

Frank Church
to Zaher Dirkey

I have managed to get the tiopf2 working. It is easier and clearer than the last time I used it. @Zaher Have you been able to get tiopf3 working on Lazarus?

Zaher Dirkey wrote 63 lines
Why you hate "master", i believe it is for last working version, here is tiOPF3, i do that, and for me it have all fixes in it, so who need last of every thing he will take "master". On Sat, Apr 6, 2013 at 3:06 AM, Graeme Geldenhuys < > wrote: > On 2013-04-05 18:03, Frank Church wrote: > > > > Which branch should I checkout to use with Lazarus? > > tiOPF2 branch. > > FPC still can't compile the tiOPF3 branch, due to Unicode and other > Delphi language features. Feature wise, tiOPF2 and tiOPF3 are near > identical, and I keep them in sync. > > > The information on the > > website is bit confusing. > > The tiOPF website or the FPC/Lazarus wiki? > > I just updated the FPC/Lazarus wiki page with the latest information. > > http://wiki.lazarus.freepascal.org/tiOPF > > > > The tiopf2 branch appears to date back to 2008 > > Uh? The latest commit was done today. > > > Regards, > - Graeme - > > -- > fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal > http://fpgui.sourceforge.net/ > > > -- > _______________________________________________ > Lazarus mailing list > > http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus > -- I am using last revision of Lazarus, FPC 2.6 on Windows XP SP3 Best Regards Zaher Dirkey -- _______________________________________________ Lazarus mailing list http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Frank Church ======================= http://devblog.brahmancreations.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20130406/5e1527a3/attachment.html>

Reply by email

Graeme Geldenhuys
to Zaher Dirkey: Why you hate "master", i believe it is for last working version, here is tiOPF3, i do…
Zaher Dirkey wrote
Why you hate "master", i believe it is for last working version, here is tiOPF3, i do that, and for me it have all fixes in it, so who need last of every thing he will take "master".

I'm not sure I fully understand your email. But I'll explain what I think.

I don't "hate" the 'master' branch concept of Git. The way the tiOPF SubVersion repository was structured (very different to the normal SubVersion layouts), it was very hard to import the history into Git. Also in the tiOPF project there are two active branches being developed in parallel at the moment. Normally projects branch major versions, and older versions are not developed any more. This is NOT the case in tiOPF. FPC users can't move to tiOPF3 branch yet (at least last time I tested), due to FPC missing Delphi language features. So two branches (tiopf2 & tiopf3) are developed and maintained in parallel.

So there is no single development branch in tiOPF. That is why I decided to make 'master' an non-development branch. Git seems to expect a 'master' branch though (which I think is wrong design). So instead of me choose if 'master' must be v2 or v3 of tiOPF, I rather made it an entry point which just contains a README file explaining the repository layout. If the developer uses Free Pascal, switch to 'tiopf2', if they use Delphi 2009+, then switch to 'tiopf3' branch.

Regards,
- Graeme -

fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://fpgui.sourceforge.net/

Reply by email