| 4 Oct 2024 |
autra | we can just propagate it like that: https://github.com/NixOS/nixpkgs/compare/master...autra:nixpkgs:qgis_unwrapped_param
That'll work, right? | 09:28:56 |
Ivan Mincik (imincik) | In reply to @autra:trancart.eu we can just propagate it like that: https://github.com/NixOS/nixpkgs/compare/master...autra:nixpkgs:qgis_unwrapped_param
That'll work, right? Yes, this works and I am not personally against this approach. | 09:30:24 |
autra | a bit of boilerplate.... but simple and straight to the point. | 09:30:36 |
Ivan Mincik (imincik) | If nobody comes with a better idea I am OK with that. | 09:31:05 |
autra | for me, that works best for things that are actually set at compile time (like grass, if I understand correctly), also because the number of possibilities is limited | 09:31:51 |
autra | this doesn't really work for plugins that needs a native counter-part, like saga | 09:32:08 |
autra | in this case, I'd maybe go for a qgisPackages.saga, which would draw the saga deps and the plugin, like we have postgresqlPackages, pythonPackages... | 09:32:46 |
autra | maybe a bit more involved for us maintainer :-) | 09:33:03 |
autra | but it opens up more possibility. | 09:33:18 |
autra | (again, if I understand things correctly about this construction) | 09:33:31 |
Ivan Mincik (imincik) | In reply to @autra:trancart.eu in this case, I'd maybe go for a qgisPackages.saga, which would draw the saga deps and the plugin, like we have postgresqlPackages, pythonPackages... I like this idea. | 09:33:37 |
autra | the only challenge I see, is that we might be tempted to start packaging a lot of plugins then. Exactly like python, which basically "duplicates" part of pypi. I'm not against that, but it might need a bigger workforce I don't know | 09:35:07 |
autra | might be bigger than we can chew | 09:35:31 |
Ivan Mincik (imincik) | It would be really great if we could discuss things like that as a team. For long I am thinking about team video call. Not sure if people would like it. | 09:39:58 |
autra | No problem for me :-) It could help brainstorm, at least. | 09:41:45 |
autra | some oss projects do regular dev meetings, not necessarily limited to team members btw, for instance. | 09:42:20 |
autra | but timezones, availabilities and tastes make it so that you'll never have everybody of course | 09:42:47 |
Ivan Mincik (imincik) | I would be very happy to talk to all people interested in geospatial packaging. I can try to propose it via discourse and other channels to see who is interested. | 09:44:02 |
autra | And on a completely unrelated topic, about the libxml2 thing, where should I post to ask what to do? Discourse? An issue on gh? On the issue about 24.11 blockers? | 09:46:07 |
Ivan Mincik (imincik) | In reply to @autra:trancart.eu And on a completely unrelated topic, about the libxml2 thing, where should I post to ask what to do? Discourse? An issue on gh? On the issue about 24.11 blockers? Asking for solution via Discourse looks best to me. | 13:30:19 |
| 10 Oct 2024 |
autra | did Someone dig further that story about libxml2? There is a PR removing HTTP support for libspatialite https://github.com/NixOS/nixpkgs/pull/347724 (otherwise Ill try to have a look soon, but can't guarantee a timeline :-/) | 17:17:07 |
| 12 Oct 2024 |
| @steeringwheelrules:tchncs.de joined the room. | 22:48:05 |
| 17 Oct 2024 |
Ivan Mincik (imincik) | In reply to @imincik:matrix.org Yes, this works and I am not personally against this approach. autra: https://github.com/NixOS/nixpkgs/pull/349247 | 09:49:39 |
| 19 Oct 2024 |
Tim Sutton | hey Ivan Mincik (imincik) could we meet up for an online hangout some time (happy to have an open call with other interested parties) | 12:47:50 |
Tim Sutton | On my agenda:
- Using libqgis based python apps e.g. to run pyqgis unit tests or make standalone QGIS based apps
- Adding debug symbols to QGIS builds so that we can examine core dumps properly
- Creating a proper developer environment for QGIS with QtCreator / Qt Kits / ccache etc. so that we can use NixOS as a nice development environment for QGIS itself
- I have packaged up a bunch of smaller python geospatial related python libs and tools that would be great to upstream, would be nice to know how to orchestrate sharing them (and having some review since I am a nix packaging noob)
- Other key packages that would be great to have with QGIS: OTB, WhiteBox Tools, - I've read the discussions about batteries included vs pared down packaging for QGIS. IMHO it would be nice to ship at least the same packages that QGIS ships on windows as default, but then also make some of the aforementioned tools available.
- Running multiple versions of QGIS on the same machine with discrete .desktop files and icons (e.g. putting LTR on the ltr QGIS Icon)
- Getting the QGIS widgets registered as QtDesigner plugins so that you can build UI's in designer for QGIS plugins etc
- Getting the QGIS python API to work nicely in ide's like VSCode so that you can get proper autocompletion when developing QGIS plugins etc
| 12:57:26 |
Tim Sutton | I have been building a plugin for QGIS on NixOS and above represent some of the pain points that I and no doubt others face using NixOS and QGIS | 12:58:24 |
Ivan Mincik (imincik) | In reply to @timlinux:osgeo.org hey Ivan Mincik (imincik) could we meet up for an online hangout some time (happy to have an open call with other interested parties) Sure, i am very happy to have a chat. Maybe others are interested as well -@autra:trancart.eu. | 13:50:50 |
Tim Sutton | Cool - when would suit you? Evenings or office hours? Or weekend? Any is fine for me | 15:00:22 |
Tim Sutton | Ivan Mincik (imincik): | 15:11:16 |
autra | I'm on PTO, so my schedule is a bit unpredictable, but I'd be interested to join, for sure! | 19:21:41 |