Package Registration Error

[reinerr]

I've stuffed up Lazarus! 

I tried to install Indy - first with the most recent version I had on my system (10.5.8 - which I use with Delphi). This complained about having no Register (? from memory) functions but I went ahead anyway. I then tried to uninstall it and went to Package -> Install/Uninstall Package. I found the 2 10.5.8 packages on the left and did "uninstall selection" then downloaded 10.2.0.3 from http://www.indyproject.org/Sockets/fpc/index.en.aspx

This compiled but when I tried to install it it now complained about duplicate packages "indylaz", which was annoying because I thought I uninstalled that before but obviously uninstalling it doesn't actually uninstall it.

Now after I install the 10.2.0.3 and Lazarus starts again it complains with a dialog:
Registration Error
Package: "indylaz 10.5.8"
Unit Name: "IdCoreDsnRegister"
Unit not found: "IdCoreDsnRegister"


If I go to the Package Graph it lists indylaz 10.5.8 - how do I permanently rid lazarus of any reference to the old package. I have searched for "indylaz" in the lazarus installed directory but found nothing (though Windows 7 search interface is atrocious).

[garlar27]

Have you tried to delete or rename the folder with the old version component.

One year ago I had a similar problem with ZEOS. After uninstalled the old component I renamed its folder and installed the new version component. If you get an error message, it will be easier to detect the problem

[garlar27]

If I go to the Package Graph it lists indylaz 10.5.8 - how do I permanently rid lazarus of any reference to the old package. I have searched for "indylaz" in the lazarus installed directory but found nothing (though Windows 7 search interface is atrocious).

I Forgot to mention: Lazarus config is in "c:\Documents and Settings\User\Local configuration\Program Data" or something like that (I'm sorry for translation, I don't remember the english pathway  ).

[reinerr]

thanks - found the offending file (packagefiles.xml in [homedrive]:\Users\[user]\AppData\Local\lazarus). "Item8" had a value of "indylaz" with the correct path and "Item9" also had a value of "indylaz" but with the non-working library so I cleared this and now Lazarus starts without errors.

[picstart]

I had a similar problem a week ago. IMO we have taken a turn towards an uncertain future. There was a time when an IDE needed the units a form descriptor and a project file 3 file types and they were at the feet of the programmer. Now we are in an  "Alice in Wonderland" world where c:\Documents and Settings\User\Local configuration\Program Data on one Microsoft OS is something else on another like win7 which is heading toward file virtualization where the location of the file is an abstraction in Libraries. The IDE sequesters information in XML files that have uncontrolled content and become the equivalent of code allowing for indirection /redirection and misdirection. The IDE instead of being the slave acts as an all knowing master that has file placement and dependencies known to itself. The IDE gains wizardry and the feeling of being in control disappears behind the magic curtain. It's true we don't control the circuit on silicon the CPU uses when it obeys the IDE wizardry but it would be nice to know everywhere the IDE squirrels away information. The good news is that the final exe from a lazarus project  is still  pretty much self contained and independent of file hierarchies.

[eny]

I had a similar problem a week ago.

I too disliked the settings Lazarus kept in a well hidden (under Window$) user folder. Corrupting new installs and playing tricks on you when changing lazarus or FPC versions.
The -pcp (or --primary-config-path) parm makes life a lot easier; all Lazarus config stored in a well known location (i.e. a location you define yourself!).

[picstart]

Eny, I really need to feel I have some control over lazarus ...I'd like to install lazarus 9.30 in a directory lazarus_9.30 and have other versions say lazarus 9.26 in lazarus_9.26 and not have any dependencies leak out of these directories into areas like win7 libraries. This way there is no interdependency between the versions and backups are certain and assured to get all there is. The lazarus installers are impolite in that they place things in directories I haven't specified even though I have specified a specific directory in response to the installer prompt. Sure Microsoft encourages this ( user library forced behavior) but it isn't polite. You invite someone into your living room and next you find they are putting things in your closet.  I don't understand how to defeat this.  You mentioned -pcp . How do I make the installer a good guest and only stay in the directory it was invited into? An example of using -pcp with an installer will help. AFAIK Lazarus doesn't spread to program files and System32 etc at least not yet so that's a plus.

[marcov]

Eny, I really need to feel I have some control over lazarus ...I'd like to install lazarus 9.30 in a directory lazarus_9.30 and have other versions say lazarus 9.26 in lazarus_9.26 and not have any dependencies leak out of these directories into areas like win7 libraries. This way there is no interdependency between the versions and backups are certain and assured to get all there is. The lazarus installers are impolite in that they place things in directories I haven't specified even though I have specified a specific directory in response to the installer prompt. Sure Microsoft encourages this ( user library forced behavior) but it isn't polite. You invite someone into your living room and next you find they are putting things in your closet.  I don't understand how to defeat this.  You mentioned -pcp . How do I make the installer a good guest and only stay in the directory it was invited into? An example of using -pcp with an installer will help. AFAIK Lazarus doesn't spread to program files and System32 etc at least not yet so that's a plus.

The installer doesn't. The ability to do  be selfcontained in a directory is a feature of Lazarus, but not available in the installer