> > Regarding side by side installations, wouldn't it be better > to store > > the lazarus config in a subdir of the lazarus install? A fixed > > directory makes side by side installation of lazarus very difficult. > You mean a --primary-config path underneath the lazarus > application directory? Could be done in principle. > > Then again, current fpcup does not have a fixed > primary-config-path, merely a default one. >
Unless I overlooked something, the primary-config-path is pretty hardcoded now (XdgConfigHome/lazarusdevsettings). Adding a parameter for primary-config-path would solve a lot. > I intended to leave the fpc and lazarus svn directories alone > as much as possible so a user could delete everything and do > a new checkout whenever he wants without touching config files. > Lazarus config files are sometimes part of the problem when working with svn. Making an all clean start would preferably also mean removing the lazarus config files. > I realize storing fpcup config files (e.g. SVN urls, etc) in > the lazarus and/or fpc svn dirs may not be desirable - if we > follow that strategy. > Why not create a fpcup script or link alongside the launcher(s) that take the same parameters as the one use to create the launcher? Something like 'lazlinkname' and 'lazlinkname Update'. Ludo > An alternative could be to use an fpcup config file stored > wherever config files are stored on the os (forgot the > function in FPC). Then use a default profile and allow the > user to add profiles (e.g. using --saveasprofile=bla). User > can invoke with --profile=bla. This will allow the GUI to > also easily retrieve a list of side-by-side installs... > > Regards, > Reinier > _______________________________________________ > fpc-pascal maillist - fpc-pascal@lists.freepascal.org > http://lists.freepascal.org/mailman/listinfo/fpc-pascal > _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
