![]() |
Re: [Announce] Native offline maps: OSM Scout Server
Quote:
|
Re: [Announce] Native offline maps: OSM Scout Server
Quote:
Quote:
Quote:
For example, the recent Storeman and crypto-sdcard RPMs are provided in SFOS-version specific releases in a single RPM-repository. I documented how to handle this (primarily for myself) in crypto-sdcard's "Release version format, RPM dependencies and Git workflow". Suggestions, enhancements, constructive criticism, etc. are welcome, as always. |
Re: [Announce] Native offline maps: OSM Scout Server
Sorry a naive question from an old geezer with only a shallow understanding of Linux and its distribution systems.
Does it need to be SFOS-version specific? If let's say a patch updates let's say the SMS app version x.yy.zzz, isn't it a bit of an overkill to make it depend on a specific version of SFOS, rather than, more logically, on a specific version of the SMS app? Will pkcon/zypper not work it out in such a case? |
Re: [Announce] Native offline maps: OSM Scout Server
Quote:
I gather from your comment that this is a known issue, maybe it was already mentioned elsewhere. Quote:
Be that as it may, ~50 times a second seems too much, but otoh there might be a good reason for that. |
Re: [Announce] Native offline maps: OSM Scout Server
Quote:
(10chars) |
Re: [Announce] Native offline maps: OSM Scout Server
@olf: I must say it is fast becoming rather elaborate in terms of trying to support multiple SFOS versions with several packages. I prefer to offload this to the users and provide such support using OBS repos. There is limited time that has to be taken into account and, in this context, I prefer to distribute the workload instead of piling it all on myself.
@nonsuch: something has to access it to make it happen. It could be any other client that you could have been running (modRana, sports app). Don't know what else could it be. I guess that you had somehow a server version installed which could not be launched. Why, no idea. And systemd tried to launch it - many times. Alternative is that socket activation script was left behind after uninstall. But I would expect systemd to check for availability of executable before starting it. Please file it as an issue, so I would remember to look into it. |
Re: [Announce] Native offline maps: OSM Scout Server
Quote:
You are right that if the SMS app changes "a != null" for "null != a", it will not affect those dependencies/requirements, and thus all packagers will find it trivial to update it; however, if an upgrade now requires the availability of e.g., the library to access sqlite databases, each OS/distro will have to adjust accordingly. OS2/Warp (*wink* *wink*) would find it probably impossible, while others will have it provided already and perhaps something like Gentoo Linux will just add a build dependency. So, it isn't possible to do what you ask unless everybody agrees on a ubiquitous packaging system that does all this for you and works everywhere. I could quote a couple of examples where this "kind of" works at a generic level, but it will a) spark a lot of debate and b) will be very off topic. Lastly, the examples above (dependencies/sys requirements) don't cover everything that is to be taken into account, there are a lot more things :) |
Re: [Announce] Native offline maps: OSM Scout Server
@nonsuch: I have opened an issue https://github.com/rinigus/osmscout-server/issues/343
Re dependencies: fortunately, RPM SPEC deps are frequently detected automatically. So, large part of it is done for us. But to support multiple SFOS version from single repo, I would have to have all RPMs with unique names and ensure that they don't clash (sometimes same RPM can be installed in multiple SFOS versions). |
Re: [Announce] Native offline maps: OSM Scout Server
Quote:
I just wanted to point out, that it is technically feasible (which was @pichlo's original question), used in practice at Openrepos, and does not need multiple RPM-repositories. |
Re: [Announce] Native offline maps: OSM Scout Server
Quote:
|
All times are GMT. The time now is 23:25. |
vBulletin® Version 3.8.8