On 31/03/2011 13:02, Andreas Schneider wrote: > Sorry, but a newbie shouldn't juggle with a bunch of lazarus > installations of different versions in the first place. Either you > know what you are doing, or you don't. In the latter case: stay away > from it until you do :D > What about a casual user, who is somewhat familiar, usually runs and uses stable snapshots of both FPC and Laz and wants to try new Lazarus/FPC pair version without removing the old one first (e.g. using lazarus from SVN) to see whether his program will still be compiling/running, even if he's not going to put this version of Laz/FPC into production YET...? (and, not willing to use another physical/virtual machine for this purpose...) (trivial example : Juha's work on Lazarus interface... or the new features of FPC 2.5.X)
I'd like to try that, but >for me< the threshold is a tad too high to understand and perform this in say 15 minutes, on a non-trivial project? (here I assume I will do a special SVN checkout of my project to a different working directory, intended only for non-production use) > I don't say it would be nice to have a friendlier solution, but it's > definitely not that important - there are more important things than > supporting multiple concurrent installations out-of-the-box (in a > newbie-friendly way). See above. I'd happily try even SVN of FPC/Laz without it eating up my production environment. > > However, it is indeed very important to verify the validity of the > configs, since the case you mentioned (upgrading lazarus and then > having the wrong compiler paths etc.) is not that uncommon and indeed > can hit newbies pretty hard. > Not just any newbies. Maybe just newbies-to-Lazarus-development, that. L. -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
