Yes, while the MSYS BSDDB3 package was unavailable for some time, my PR was accepted by the MSYS2 maintainers and it was re-introduced in time for Gramps 5.2.0. It is included in Gramps AIO on Windows so that is not the limitation. As far as I know bsddb3 support was removed intentionally (it’s in the FAQ and NEWS). I am not aware of the capability being moved to an addon.
bsddb3 supports up to Python 3.9. It will not support Python 3.10.
Could it be that it is missing in the Gramps AIO for 5.2.2? At least when I installed 5.2.2, there was no BSDDB in the options for database backends.
I’m no Python guy so I simply do not have any idea what’s the consequence of that 3.9 vs 3.10 issue might be. The only thing I know for sure is that after the installation of 5.2.2 on my Win10/64 machine, there was no BSDDB available in the options for database backends. My understanding based on discussions here in the forum was that a decision has been made to stop supporting BSDDB as database backend. That’s basically fine with me since I feel that Gramps should use modern database backends now available (e g PostgreSQL), but it also means that user with large databases cannot use 5.2.2 because it is to slow.
BSDDB3 was used in the AIO build. As to why you don’t see it in 5.2 see the links below. Apparently you can open BSDDB3 databases, but not create new ones.
Officially yes, support is only till Python 3.9. However it works with newer Python versions. It’s been many months since I worked on this, but see this and later messages for additional info. Of course, because of lack of official support if there are any problems, we would have to solve them ourselves!
Ok, you’re right, I was a bit imprecise in my statement. It was possible to open my old BSDDB database from 5.1.6, but it was not possible to use BSDDB for new databases. So 5.2.2 does support BSDDB to a certain extent but since I quite frequently have to create new databases, this kind of support is not enough for me.
Using 5.1.6 on Kubuntu 22.04. So busy with so many other projects and both of these are stable, so no push to upgrade. When I get time I try to work on my brick walls.
I’m migrating from WIndows 10 to Linux Mint so use GRAMPS on both!
I would guess people that visit this forum, especially those that visit it somewhat regularly, is more likely to be developers, technical interested people, people more interested improvements that can be made in Gramps, or similar category of people, than other kinds of people that may use Gramps. It usually is the case with online forums.
And I think those kind of people is quite a bit more likely to use Linux compared to mac and windows.
Just remember that when you judge the numbers.
Download numbers would probably be more accurate numbers. But I guess the same kind of people that would regularly use this forum are also more likely to keep updating to the latest versions and therefore count as more total downloads if you combine the numbers between versions.
Note: I am not saying that is the case with everyone, at all, just percentage wise.
My point is that this post a lone, give a lot more information about the user-base of this forum, than it does about the user-base of Gramps itself.
Possibly. But there are SO many download channels that they are difficult to track and collate.
My thought is that the most accurrate number for advanced users of 5.1 and earlier would come from the GitHub addon repository touches. (The users who avoid addons wouldn’t be represented.)
And 5.2 polls the repository without user permission and action. So it should get a more accurate sampling of the users where Gramps is allowed internet access.
The project would just need to collect data on visitors.
Oh, I didnt know that, yes, statistics reporting inside of Gramps would be the most accurate, even if some use it without internet access.
Updating the script that checks for updates to log the action on a GRAMPS server with the date and host name (or other info if necessary) could be used to get a better count on the number of versions still in service.
A post was split to a new topic: Install from source
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.