<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 12/08/2021 15:11, Bo Berglund via
fpc-pascal wrote:<br>
</div>
<blockquote type="cite"
cite="mid:gu6ahgdh957kr6haoj33j6oa4ehmue70pi@4ax.com">
<pre class="moz-quote-pre" wrap="">On Wed, 11 Aug 2021 23:13:28 +0200, Martin Frb via fpc-pascal
<a class="moz-txt-link-rfc2396E" href="mailto:fpc-pascal@lists.freepascal.org"><fpc-pascal@lists.freepascal.org></a> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Well I don't know your script, and I am not sure how exactly you do that
in svn....
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
It is not done in SVN, instead I visit the (now removed) page
<a class="moz-txt-link-freetext" href="https://svn.freepascal.org/svn/lazarus/">https://svn.freepascal.org/svn/lazarus/</a> (for lazarus)
or
<a class="moz-txt-link-freetext" href="https://svn.freepascal.org/svn/fpc/">https://svn.freepascal.org/svn/fpc/</a> (for fpc)
and look at the tags list to find the most recent release tag.
I then use that as input to my script.</pre>
</blockquote>
ok, so you could run<br>
git ls-remote <br>
in your shell, and look at that. <br>
<br>
<blockquote type="cite"
cite="mid:gu6ahgdh957kr6haoj33j6oa4ehmue70pi@4ax.com">
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Also I do not know, if this is for a once up setup (so you only wont to
download the one revision and nothing else), or if you don't mind.
(I have not measured the overhead..>)
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
It is for installation on a pristine RaspberryPi (or Ubuntu) machine and the
script does everything including setting up the folder tree for development and
adding the desktop shortcuts.
Of corse now it is unusable because it cannot retrieve the sources... :(
I want to download the complete source tree for the tagged revision I want to
install. I do not care if it is with metadata or not, I only ever use the files
as is and never modify them.</pre>
</blockquote>
<br>
Well <br>
<div class="moz-cite-prefix">On 12/08/2021 08:12, Christo Crause via
fpc-pascal wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAGOmfbE99VVPWPBtFCzmtckO57=qk58kKspuEeSW9mxUE1G3uw@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">git clone --depth=1 --branch fixes_3_2
--single-branch <a
href="https://gitlab.com/freepascal.org/fpc/source.git">https://gitlab.com/freepascal.org/fpc/source.git</a>
fpc-fixes_3_2<br>
</div>
</div>
</blockquote>
You need to test, if it works with tags too (my 3 step solution
did).<br>
<br>
<br>
<blockquote type="cite"
cite="mid:gu6ahgdh957kr6haoj33j6oa4ehmue70pi@4ax.com">
<pre class="moz-quote-pre" wrap="">
Of course I do not want to get excessive overhead like the complete history of
all files for eternity...
No history at all would be fine.</pre>
</blockquote>
depth=1<br>
<br>
Only when you update, then you do get history.<br>
<br>
with my "fetch" solution<br>
<br>
git init .
<br>
git fetch --depth=1 <a class="moz-txt-link-freetext"
href="https://gitlab.com/freepascal.org/lazarus/lazarus.git">https://gitlab.com/freepascal.org/lazarus/lazarus.git</a>
refs/tags/lazarus_2_2_0_RC1
<br>
git switch -c my-branch FETCH_HEAD
<br>
<br>
you can then later do (may download entire 2.2.0, NOT just the diffs
/ if you are lucky it will reuse some of your local existing data /
I don't know the internals well enough)<br>
<br>
git fetch --depth=1 <a class="moz-txt-link-freetext"
href="https://gitlab.com/freepascal.org/lazarus/lazarus.git">https://gitlab.com/freepascal.org/lazarus/lazarus.git</a>
refs/tags/lazarus_2_2_0<br>
git switch -c my-NEW-branch FETCH_HEAD
<br>
git branch -d my-branch<br>
git reflog expire --expire=now --all <br>
git gc --prune=now --aggressive<br>
<br>
And then you should have just the new branch, and all old data gone.
But you temp have both.<br>
(git switch takes -f to overwrite changed file / there also is a
merge option instead)<br>
<br>
Afaik You only can get rid of the old data, once you switched to the
new. So for a brief moment you do have both.<br>
<br>
Or you delete the entire dir, and start from scratch.<br>
<br>
</body>
</html>