How to (correctly) update with OPM?

[polpero]

I thought I understood the way to update with the Online Package Manager
But now I am in doubt...

Let's say some changes have been made to ATSynEdit
What would be the correct way, using the OPM, to proceed?

I am now copying the files manually downloaded from ATSynEdit's GitHub
and placing them in the package repository used by OPM
but that's not the correct way to do it right?

I won't mention the other attempts made prior to this one...


 

[balazsszekely]

Hi polpero,

Please read this: https://wiki.freepascal.org/Online_Package_Manager

PS: I updated ATSynEdit, ATSynEdit_Ex, ATSynEdit_Cmp, EControl, ATflatcontols

[JuhaManninen]

I am now copying the files manually downloaded from ATSynEdit's GitHub
and placing them in the package repository used by OPM

You should get a component's sources from its development repository, in this case clone from Github, and install directly without OPM.
OPM provides release versions but you follow the development of some components more closely and want to test every change.

[jcmontherock]

I read the wiki page given by GetMem and I have one question:
What the meaning of the blue icon at the left of package name ? There is no hint.

[balazsszekely]

I read the wiki page given by GetMem and I have one question:
What the meaning of the blue icon at the left of package name ? There is no hint.

Shows newly added/updated package(s) for 31 days. The number of days can be configured in options(see attached image).

[wp]

You cannot "update" a component installed by OPM, you only can re-install it. So when OPM shows you by means of the blue arrow that there is a new version and you want to update your current installation, check and install the package as if it were your first installation of it. At the end you will have the new version in the IDE.

However, you will only get the OPM version this way. As Juha noted this is always the most recent stable version released by the author. In order to get the most recent development version install the package from its repository, usually svn or git, and this will overwrite a previously installed OPM version. Installation from the repository is a bit more complicated than the one-click process of OPM: download the package via svn or git, or download the zipped sources, then open the .lpk file found in the package. When it is a designtime-package you must also click "Use">"Install" and rebuild the IDE. Sometimes there are several packages within the same download; here you must handle the packages in the correct order - have a look at the README file which often accompanies the download.

[jcmontherock]

Thanks for your explanations   

[polpero]

@wp

Your last paragraph is the confirmation I was looking for,
and what a method of trial and error finally brought me to.

This last paragraph of yours should be added to the wiki page.

//

This also means that such an update 'messes' with the OPM's work
as a re-installation by the OPM of such a component
would  remove the update and require also a re-updating...

Thanks for the information.

[wp]

This also means that such an update 'messes' with the OPM's work
as a re-installation by the OPM of such a component
would  remove the update and require also a re-updating...

It does not matter how you install a package, it always replaces the previously installed version and makes the new version available (the old source files, however, are left unchanged if they are in a different folder). This is no "mess". Luckily the IDE is able to always (*) find the most recently installed version.

----
(*) Disclamer: Never make absolute statements such as "always", "never" etc