<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 27/09/2013 22:30, Kjow wrote:<br>
</div>
<blockquote
cite="mid:CADatRmiFxw64KuD2RM8TQHx6qUExwHfDcA1E3n63ynu2CDTBAQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>I never understood which svn to download for stable
"homemade buildings".<br>
</div>
</div>
</div>
</blockquote>
I'll list my preferences below ;)<br>
<blockquote
cite="mid:CADatRmiFxw64KuD2RM8TQHx6qUExwHfDcA1E3n63ynu2CDTBAQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div><br>
About trunk:<br>
<br>
FPC -> <a moz-do-not-send="true"
href="http://svn.freepascal.org/svn/fpc/trunk/">http://svn.freepascal.org/svn/fpc/trunk/</a><br>
</div>
</div>
</div>
</blockquote>
FPC trunk right now is not terribly stable because of the big
unicode changes coming in. That said, I do use it myself for FPC
development/patches, and hobbyist projects. In case of problems
either revert to a known working revision or just use a downloaded
stock Laz 1.0.12+FPC 2.6.2 combination that I have installed anyway.<br>
I use fpcup so I can fairly easily manage multiple independent Laz
installs but I might have mentioned that before ;)<br>
<blockquote
cite="mid:CADatRmiFxw64KuD2RM8TQHx6qUExwHfDcA1E3n63ynu2CDTBAQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
Lazarus -> <a moz-do-not-send="true"
href="http://svn.freepascal.org/svn/lazarus/trunk/">http://svn.freepascal.org/svn/lazarus/trunk/</a><br>
</div>
</div>
</div>
</blockquote>
For home use, I would definitely use Laz trunk. In general it's
quite stable, and sees a lot of improvements and fixes.<br>
<blockquote
cite="mid:CADatRmiFxw64KuD2RM8TQHx6qUExwHfDcA1E3n63ynu2CDTBAQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div><br>
About stable tree, which?<br>
FPC:<br>
<a moz-do-not-send="true"
href="http://svn.freepascal.org/svn/fpc/branches/fixes_2_6/">http://svn.freepascal.org/svn/fpc/branches/fixes_2_6/</a><br>
</div>
</div>
</div>
</blockquote>
If you don't choose FPC trunk I would choose this one as it gets
fixes over existing stable FPC 2.6.x (currently FPC 2.6.2) and
therefore should be more bug free.<br>
<blockquote
cite="mid:CADatRmiFxw64KuD2RM8TQHx6qUExwHfDcA1E3n63ynu2CDTBAQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div> <br>
</div>
</div>
</div>
</blockquote>
<blockquote
cite="mid:CADatRmiFxw64KuD2RM8TQHx6qUExwHfDcA1E3n63ynu2CDTBAQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div><a moz-do-not-send="true"
href="http://svn.freepascal.org/svn/fpc/tags/release_2_6_2/">http://svn.freepascal.org/svn/fpc/tags/release_2_6_2/</a><br>
<br>
Lazarus:<br>
<a moz-do-not-send="true"
href="http://svn.freepascal.org/svn/lazarus/branches/fixes_1_0/"><snip></a><br>
</div>
</div>
</div>
</blockquote>
I'd just use trunk.<br>
<blockquote
cite="mid:CADatRmiFxw64KuD2RM8TQHx6qUExwHfDcA1E3n63ynu2CDTBAQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>...and then, when a new version is released, I need to
download an other svn url, deleting the old one? </div>
</div>
</div>
</blockquote>
Well.... yes, that is an option. See below though.<br>
<blockquote
cite="mid:CADatRmiFxw64KuD2RM8TQHx6qUExwHfDcA1E3n63ynu2CDTBAQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>Can I upgrade?<br>
</div>
</div>
</div>
</blockquote>
(untested, by memory) you could do an svn export of your existing
directory to a new dir, then delete the old one (or a more hackish
way that avoids copying: remove all .svn subdirs and any other svn
files in your currerent directory).<br>
<br>
Now you probably have most of the files, but you need to get the svn
repo info/metadata as well as all updates/deletions/additions.<br>
do an svn checkout for the new url specifying the new directory. You
probably will need to use --force or something as it will complain
about the directory already existing, being non-empty etc.<br>
<br>
Then do an svn update for good measure. Shouldn't really be
necessary, but it can help.<br>
<br>
<blockquote
cite="mid:CADatRmiFxw64KuD2RM8TQHx6qUExwHfDcA1E3n63ynu2CDTBAQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<br>
Is there something similar to trunk tree (only one url) that
is always updated to the latest revision/version?<br>
</div>
</div>
</div>
</blockquote>
Per definition trunk is always updated.<br>
However, one of the *fixes branches would be an option if you want
to get new fixes and less chances of bugs.<br>
</body>
</html>