Upgrade SQLinForm to 5.3.24 failed
-
OK, thanks for the info. It means the admin will to the merge.
is this happening once every week or so?
Regards
Guido -
AFAIK you would have to do something called a “pull request” to get this merged.
-
The update will be not available immediately but together with the next N++ release.
-
@chcg said:
The update will be not available immediately but together with the next N++ release.
with my 30+ years of programming experience I still cannot guarantee to deliver error free software :-( Therefore I would really appreciate to have the possibility to publish a hot fix in a quicker way as waiting for the next N++ release which could take a couple of months. What do you think?
-
@Guido-Thelen said:
with my 30+ years of programming experience I still cannot guarantee to deliver error free software
Okay, so that is true, but what does it have to do with anything?
have the possibility to publish a hot fix in a quicker way as waiting for the next N++ release which could take a couple of months
That’s just not the way it works with Notepad++, sorry. However, the source code is available and you could build your own patched version until a release with the change integrated happens.
-
Thanks, Alan,
so, it means a new plugin version is published together with the publisshing of a new N++ version e.g. the SQLinForm 32 bit plugin version 5.3.19 was published with N++ 6.1 and the next SQLinForm 32 bit version (5.3.24) will be available with next N++ version. Then I misunderstood the Plugin Admin Tool. I thought that the plugins can be published independently from N++ publishing.
Regards
Guido -
so, it means a new plugin version is published together with the publisshing of a new N++ version e.g. the SQLinForm 32 bit plugin version 5.3.19 was published with N++ 6.1 and the next SQLinForm 32 bit version (5.3.24) will be available with next N++ version.
that’s a very good question.
i didn’t look at the updater code until now and i’ve assumed that%ProgramData%\Notepad++\plugins\config\nppPluginList.dll, which contains the json plugin listpl.x86.jsonfrom here, orpl.x64.jsonfrom here, is updated every time that you invoke plugins admin … but it is not.@chcg 's statement, @Alan-Kilborn’s emphasising, and your description of it are completely right, the plugin list inside of nppPluginList.dll was, to date, only updated at downloading a new version release.
i did a crosscheck, to make sure i did not misread any code parts due to lack of knowledge:
i’ve put an old 7.6.0 nppPluginList.dll into a 7.6.2 installation and it does not get updated.but maybe @donho can help us to explain any problems that caused this way of implementation while coding, and/or to share/brainstorm current ideas of making the plugins list independent to a full release.
-
The current behaviour of PA is an intermediate state to my understanding and a separate update cycle for the plugin list will be implemented in the future. Right know the focus I guess is more on providing a first usable version of the plugin admin system.
The plugin manager already had this functionality (at least for the dev list) to provide the updated list after the change almost immediately. -
Hi @chcg ,
do you have any news about the update cycle for the plugin list. I intend to publish a new version from my plugin. Just wondering if it will available only with next N++ release.
Regards
Guido -
@Meta-Chuh and all
The reason for @bruderstein to include some advertisement into his Plugin Manager was the high server traffic generated by solely the download of the plugin list - 70 GB per month as he stated somewhere.
His web hoster refused to continue that for free and GitHub wanted 80 Euro per month to host this file, which Dave was not willing to pay, additionally to all the work and time he invested in development of Plugin Manager.
So Dave asked his employer to host the plugin list file. They have been willing to do that but wanted their logo to be placed into Plugin Manager, which was the reason for Don to kick it out of the Notepad++ downloads.
Providing an all-time up-to-date plugin list for Plugins Admin will cause the same problem again. Let’s see how it will be solved…
Furthermore, AFAIK Notepad++ checks the SHA-256 hash value of the plugin list’s DLL file against a value hard coded into each Notepad++ release. This will not work anymore in case of continous updating that file. When I see the security issues that have been raised in the EUFOSSA bug bounty program for Notepad++, I suspect that a completely unprotected plugin list would also be considered a security issue.
