> @eht16 OK (especially if you plan to have the Geany web site static).
I guess we will keep a small Django site anyway for the Pastebin service and
even if not this won't be the problem.
> @techee if you release a bugfix maybe you need to version it 2.0-1 like
> Ubuntu does with its packages.
> @techee if you release a bugfix maybe you need to version it 2.0-1 like
> Ubuntu does with its packages. Not sure it the plugin needs updating to
> handle that.
Yes, but how to get this version "inside" the package so the updatechecker
plugin knows it's 2.0-1 and can compare it with what the
@techee if you release a bugfix maybe you need to version it 2.0-1 like Ubuntu
does with its packages. Not sure it the plugin needs updating to handle that.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1314#issuecomment-2212866430
You are
@eht16 OK (especially if you plan to have the Geany web site static).
For macOS and Windows we'd have to decide how to detect the updated installer -
let's say I make a new macOS release now with updated GTK fixing some bug - the
version will still be 2.0 and the only other thing I see we could
> My thinking is that if we make a bug in the plugin's update logic, we'll have
> to make a new release to fix it while we can update the server's code any
> time without any release and it also offers more flexibility in case we need
> to change something in the future.
This is a good point.
Maybe make it a TOML file (see https://github.com/geany/geany/issues/1268)
:smiling_imp:
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1314#issuecomment-2197803050
You are receiving this because you are subscribed to this thread.
Message
Well since the plugin is really only any use for Mac and Windows since we don't
make any *x releases I guess its between you and @eht16 who conveniently is the
infrastructure manager too :-)
--
Reply to this email directly or view it on GitHub:
My thinking is that if we make a bug in the plugin's update logic, we'll have
to make a new release to fix it while we can update the server's code any time
without any release and it also offers more flexibility in case we need to
change something in the future.
--
Reply to this email
I was avoiding having any smarts in the server, just have it return a file,
which could even be served from github. If we don't want a new release to be
used we just don't put the number in the file. And that way you can modify the
Mac version without any server support by PRing the file.
> Yeah, then it can reply:
> 2.1.0
> Macos 2.1.0.1
> Windows 2.0.0.
I was actually thinking the plugin would send e.g.
```
platform: macOS
version: 2.0.0
build_date: 2024-06-21
```
and the server would only reply `TRUE` or `FALSE` based on whether the update
is available for the given
> probably require a new URL, such as https://geany.org/service/version/v2.
Yeah, then it can reply:
```
2.0.0
Macos 2.0.1
Windows 2.0.
```
so then Mac and Windows fixes can be uploaded separately. (the first is latest
release tagged in Git/tarballed, it can't be "Linux" because we don't
I managed to get the update checker plugin running (didn't really do anything,
it started working with the latest library versions from gtk-osx). So I might
add it to the next macOS release.
> I thought I had seen @techee make bugfix builds on the geany-osx repository,
> I guess if they get
Just to note what the expectation of many users may be, both Chrome browser and
Vscode IDE update checkers indicate a new version in app, and when triggered to
update can indicate if its available by an "alternate channel" which means the
distro normal update mechanism rather than direct from
> AFAIK Geany is not mainly distributed via some sort of repository like "brew"
> or so but via downloadable installers from our website and so I thought the
> update checker plugin would do the same job on Macos as on Windows.
I thought I had seen @techee make bugfix builds on the geany-osx
> The update checker for Linux works incorrectly, it checks the Geany
> repository for a new version, not the repositories for the current distro.
> Most distros don't update versions of software like Geany on LTS versions for
> example. So it just feeds frustration for users of such
I'd say
See https://github.com/geany/geany-osx/issues/53#issuecomment-1978795993
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1314#issuecomment-1979741533
You are receiving this because you are subscribed to this thread.
Message ID:
The update checker for Linux works incorrectly, it checks the Geany repository
for a new version, not the repositories for the current distro. Most distros
don't update versions of software like Geany on LTS versions for example. So
it just feeds frustration for users of such systems as they
17 matches
Mail list logo
