Recent

Author Topic: FPC & Lazarus moving to gitlab  (Read 69114 times)

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 7384
  • Debugger - SynEdit - and more
    • wiki
FPC & Lazarus moving to gitlab
« on: June 22, 2021, 07:51:24 pm »
Hello All,

The Free Pascal and Lazarus teams are in the process of switching to Gitlab to manage their source code and issue reports.

In order to lower maintenance of their own infrastructure, a hosted solution
has been chosen, and an open source license was granted to the teams.

You can see the current progress at:

https://gitlab.com/freepascal.org

2 subgroups have been made:

https://gitlab.com/freepascal.org/fpc
https://gitlab.com/freepascal.org/lazarus-ide

Several testconversions of the SVN history to a Git repository have been
done, with ever improving results. All repositories will be switched to git.

A program has been written to convert Mantis bug reports to Gitlab issues;
it is very complete, and all available info will be converted.
You can see (partial) conversion results on the above projects.

The date for the final conversion has been established as the weekend of
17/18 july. People that wish to report bugs after that will have to create a
gitlab account in order to do so. (Those with a github account can normally
also use that account to log in with gitlab, see the gitlab login page.)

The conversion program will attempt to convert existing bugs using the
account of the new gitlab user. To map your gitlab user name (or ID) to the
mantis user, we ask that you file an issue in the mantis project of the
current bugtracker, assign it the category gitlab, and set the summary of
the bugreport to your gitlab account name or ID number (not both!).
https://bugs.freepascal.org/bug_report_page.php?project_id=4

All accounts that can be collected in this manner by 17 july will be used in the final conversion.

All necessary information to connect to gitlab will be collected in the FPC &
Lazarus Wiki. Several pages have already been set up:

https://wiki.freepascal.org/FPC_git
https://wiki.freepascal.org/FPC_git_concepts
https://wiki.freepascal.org/SVN_to_GIT_Cheatsheet

These pages will be updated with the correct URLS when the final conversion happens. The FPC & Lazarus websites will also be adapted with new instructions.

For the FPC & Lazarus teams,
Martin (Message originally by Michael)
« Last Edit: June 27, 2021, 07:42:45 pm by Martin_fr »

Fred vS

  • Hero Member
  • *****
  • Posts: 2387
    • StrumPract is the musicians best friend
Re: FPC & Lazarus moving to gitlab
« Reply #1 on: June 22, 2021, 08:11:24 pm »
  :)   ;)   ;D

Fre;D
I use Lazarus 2.0.6 32/64 and FPC 3.2.0 32/64 on Debian 10.2 64 bit, Windows 10, Windows 7 32/64, Windows XP 32,  FreeBSD 64 and Mac OS X Snow Leopard 32.
Widgetset: fpGUI, MSEgui, Win32, GTK2, Qt, Carbon.

https://github.com/fredvs
https://gitlab.com/fredvs

MarkMLl

  • Hero Member
  • *****
  • Posts: 3030
Re: FPC & Lazarus moving to gitlab
« Reply #2 on: June 22, 2021, 08:32:01 pm »
Does this mean that it will no longer be possible to refer to a particular stage of trunk development as "revision such-and-such", and to step forwards and backwards from that point using a contiguous sequence of revision numbers?

MarkMLl
Turbo Pascal v1 on CCP/M-86, multitasking with LAN and graphics in 128Kb.
Pet hate: people who boast about the size and sophistication of their computer.
GitHub repositories: https://github.com/MarkMLl?tab=repositories

Fred vS

  • Hero Member
  • *****
  • Posts: 2387
    • StrumPract is the musicians best friend
Re: FPC & Lazarus moving to gitlab
« Reply #3 on: June 22, 2021, 08:38:04 pm »
Does this mean that it will no longer be possible to refer to a particular stage of trunk development as "revision such-and-such", and to step forwards and backwards from that point using a contiguous sequence of revision numbers?

MarkMLl

This?
I use Lazarus 2.0.6 32/64 and FPC 3.2.0 32/64 on Debian 10.2 64 bit, Windows 10, Windows 7 32/64, Windows XP 32,  FreeBSD 64 and Mac OS X Snow Leopard 32.
Widgetset: fpGUI, MSEgui, Win32, GTK2, Qt, Carbon.

https://github.com/fredvs
https://gitlab.com/fredvs

dr2e

  • Newbie
  • Posts: 1
Re: FPC & Lazarus moving to gitlab
« Reply #4 on: June 22, 2021, 08:41:13 pm »
The Free Pascal and Lazarus teams are in the process of switching to Gitlab to manage their source code and issue reports.
10MB ought to be enough for anybody, yeah.

MarkMLl

  • Hero Member
  • *****
  • Posts: 3030
Re: FPC & Lazarus moving to gitlab
« Reply #5 on: June 22, 2021, 08:59:36 pm »
Does this mean that it will no longer be possible to refer to a particular stage of trunk development as "revision such-and-such", and to step forwards and backwards from that point using a contiguous sequence of revision numbers?

MarkMLl

This?

Thank you Fred, I presume you mean that the sequential revision numbers will no longer exist but I would appreciate confirmation.

MarkMLl
Turbo Pascal v1 on CCP/M-86, multitasking with LAN and graphics in 128Kb.
Pet hate: people who boast about the size and sophistication of their computer.
GitHub repositories: https://github.com/MarkMLl?tab=repositories

GAN

  • Sr. Member
  • ****
  • Posts: 335
Re: FPC & Lazarus moving to gitlab
« Reply #6 on: June 22, 2021, 09:40:25 pm »
Excellent news (and decision). Thank you.
Lazarus 2.0.8 FPC 3.0.4 Linux Mint Mate 19.3
Zeos 7̶.̶2̶.̶6̶ 7.1.3a-stable - Sqlite 3.32.3 - LazReport

https://searchlazarus.blogspot.com/

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 7384
  • Debugger - SynEdit - and more
    • wiki
Re: FPC & Lazarus moving to gitlab
« Reply #7 on: June 22, 2021, 09:43:48 pm »
Does this mean that it will no longer be possible to refer to a particular stage of trunk development as "revision such-and-such", and to step forwards and backwards from that point using a contiguous sequence of revision numbers?
Mainly, yes.

The exact details on the below are still being evaluated. Outcome not yet known....
There will be options with "git describe", and such give you a way to refer to a commit in a way that tells you N commits after named known point.


If you do have a commit, you can walk to its parents easily (but not its children)
SOME_HASH_OR_NAME~1

the number gives how many parents up.



MarkMLl

  • Hero Member
  • *****
  • Posts: 3030
Re: FPC & Lazarus moving to gitlab
« Reply #8 on: June 22, 2021, 10:26:49 pm »
Does this mean that it will no longer be possible to refer to a particular stage of trunk development as "revision such-and-such", and to step forwards and backwards from that point using a contiguous sequence of revision numbers?
Mainly, yes.

The exact details on the below are still being evaluated. Outcome not yet known....
There will be options with "git describe", and such give you a way to refer to a commit in a way that tells you N commits after named known point.


If you do have a commit, you can walk to its parents easily (but not its children)
SOME_HASH_OR_NAME~1

the number gives how many parents up.

In that case I'm abandoning trunk. Git is indisputably an adequate tool for collaborative work, it's not suitable for software distribution.

MarkMLl
Turbo Pascal v1 on CCP/M-86, multitasking with LAN and graphics in 128Kb.
Pet hate: people who boast about the size and sophistication of their computer.
GitHub repositories: https://github.com/MarkMLl?tab=repositories

dbannon

  • Hero Member
  • *****
  • Posts: 1532
    • tomboy-ng, a rewrite of the classic Tomboy
Re: FPC & Lazarus moving to gitlab
« Reply #9 on: June 23, 2021, 03:23:44 am »
In that case I'm abandoning trunk. Git is indisputably an adequate tool for collaborative work, it's not suitable for software distribution.

see https://github.com/graemeg/lazarus

I have been getting Lazarus Trunk from github for the last year, very easy to step back one or many 'revisions', you work with the github web page open, you can see all the IDs, scroll down and see the diffs.  I imagine gitlb will be able to do the same.

You'll love it !

Davo
Lazarus 2, Linux (and reluctantly Win10, OSX)
My Project - https://github.com/tomboy-notes/tomboy-ng

berocoder

  • Newbie
  • Posts: 4
Re: FPC & Lazarus moving to gitlab
« Reply #10 on: June 23, 2021, 06:48:56 am »
I use Github myself and assume Gitlab is similar. Very good decision!

PascalDragon

  • Hero Member
  • *****
  • Posts: 3310
  • Compiler Developer
Re: FPC & Lazarus moving to gitlab
« Reply #11 on: June 23, 2021, 09:02:25 am »
The Free Pascal and Lazarus teams are in the process of switching to Gitlab to manage their source code and issue reports.
10MB ought to be enough for anybody, yeah.

The size restriction on Mantis is 2 MB, so I don't see a problem there. If a user would need to upload that size of source (as that is what we're dealing with) in addition that being compressed then they didn't minimize the problem accordingly and we'd request them to do that anyway.

Distribution of releases will continue from our own server anyway.

In that case I'm abandoning trunk. Git is indisputably an adequate tool for collaborative work, it's not suitable for software distribution.

I really don't see the issue you have there. You pick your commit that you know works and for yourself you can even create a local tag so that you know it's your working commit. Then you fetch new commits, switch to main, check whether that's working for you and tag anew. If not you switch back to your previous tag.

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 3959
  • I like bugs.
Re: FPC & Lazarus moving to gitlab
« Reply #12 on: June 23, 2021, 09:34:56 am »
In that case I'm abandoning trunk. Git is indisputably an adequate tool for collaborative work, it's not suitable for software distribution.
There must be a misunderstanding from your side.
SVN was not used for software distribution either. It is for revision control and used by people who are interested in the project's development and/or participating in it.
Git is used for the same purpose.
Releases will be distributed as before.

A sequential revision number is gone, thus it will be useful to list date/time together with a hash ID.
Mentioning the hash ID, date/time, author and commit message of a revision gives enough information for any purpose.
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

MarkMLl

  • Hero Member
  • *****
  • Posts: 3030
Re: FPC & Lazarus moving to gitlab
« Reply #13 on: June 23, 2021, 09:50:07 am »
In that case I'm abandoning trunk. Git is indisputably an adequate tool for collaborative work, it's not suitable for software distribution.
There must be a misunderstanding from your side.
SVN was not used for software distribution either. It is for revision control and used by people who are interested in the project's development and/or participating in it.
Git is used for the same purpose.
Releases will be distributed as before.

A sequential revision number is gone, thus it will be useful to list date/time together with a hash ID.
Mentioning the hash ID, date/time, author and commit message of a revision gives enough information for any purpose.

In the case of trunk, svn was effectively being used for distribution. I've seen Git being spectacularly incapable of filling the same role, e.g. with Mycroft where the /only/ way of running it is to have a complete repo clone.

Statement of fact: I've got too much else on my plate to be prepared to continue with trunk since the change will involve learning a new toolset. Sorry.

MarkMLl
Turbo Pascal v1 on CCP/M-86, multitasking with LAN and graphics in 128Kb.
Pet hate: people who boast about the size and sophistication of their computer.
GitHub repositories: https://github.com/MarkMLl?tab=repositories

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 7384
  • Debugger - SynEdit - and more
    • wiki
Re: FPC & Lazarus moving to gitlab
« Reply #14 on: June 23, 2021, 10:55:47 am »
In the case of trunk, svn was effectively being used for distribution. I've seen Git being spectacularly incapable of filling the same role, e.g. with Mycroft where the /only/ way of running it is to have a complete repo clone.

there is a shallow clone

git clone --depth=1  url folder

And after that, you get the complete update, so yes you keep history from that point forward. But the disk usage for that in amazingly effective/low.

- I have the entire history (just git data, no checked out files / .git folder) in 227 MB.
- On the other hand the .svn folder of my svn checkout is 918 MB.

I don't have the size of a flat git clone.

To be fair, I maintain the git folder, and have it re-packed occasional. Otherwise it may be about 350ish MB. Still better that svn.
The .svn folder is whatever svn did by itself.

** EDIT: so I did a "clean up" in my svn folder and it is now 197 MB. So if you do maintenance, you save a few bytes compared to git. But my git (ever after an unmaintained period) never got even close to half as big as the svn was when unmaintained.


There is also a zip download via gitlab.
You can select any revision and get it as zip.
« Last Edit: June 23, 2021, 11:29:17 am by Martin_fr »

 

TinyPortal © 2005-2018