[Doc] Update Ubuntu ppa source for db4.8

[Fuzzbawls]

In order to cut down on ppa clutter/size, I have setup a new ppa specifically for BerkeleyDB 4 independent from the pivxd/pivx-qt ppa repositories.

This new ppa repo will be the default place to install db4.8 dependencies moving forward for LTS versions of Ubuntu. It currently has package support for Xenial, Bionic, Focal, Jammy, and the upcoming Noble LTS versions.

New CPU architecture riscv64 has been added for OS versions starting from Focal and newer.

[JohnnyLawDGB]

Can you provide details on the maintenance plan for the new BerkeleyDB 4 PPA, particularly regarding security updates, compatibility with future Ubuntu releases, and support for the riscv64 architecture? Additionally, how will the PPA be monitored for security vulnerabilities, and what is the process for reporting and addressing any potential issues that arise?

[Fuzzbawls]

Can you provide details on the maintenance plan for the new BerkeleyDB 4 PPA, particularly regarding security updates, compatibility with future Ubuntu releases, and support for the riscv64 architecture? Additionally, how will the PPA be monitored for security vulnerabilities, and what is the process for reporting and addressing any potential issues that arise?

This isn't intended to provide extended maintenance support for BerkeleyDB 4, but rather a convenient alternative to building the existing BDB4 dependency from source, and a simple migration from providing these packages in our already crowded PIVX release PPA.

Since BDB4 has no real 3rd party dependencies of it's own (technically TCL 8.6 is used to provide the TCL bindings library...something not used with PIVX), this PPA is unlikely to get security updates. However, in the event that one of Ubuntu's 1st party packages used to compile this receives a security update, there are automated notification methods in place.

Support for new (LTS) versions of Ubuntu are added when they are made available on Launchpad for building. Same with support for the riscv64 architecture (which was previously in closed beta, but has now been opened to all PPA's with support starting from Ubuntu Focal 20.04 LTS).

To reiterate: this is a developer/tinkerer resource, and not something that is targeted towards end users

[JohnnyLawDGB]

Can you provide details on the maintenance plan for the new BerkeleyDB 4 PPA, particularly regarding security updates, compatibility with future Ubuntu releases, and support for the riscv64 architecture? Additionally, how will the PPA be monitored for security vulnerabilities, and what is the process for reporting and addressing any potential issues that arise?

This isn't intended to provide extended maintenance support for BerkeleyDB 4, but rather a convenient alternative to building the existing BDB4 dependency from source, and a simple migration from providing these packages in our already crowded PIVX release PPA.

Since BDB4 has no real 3rd party dependencies of it's own (technically TCL 8.6 is used to provide the TCL bindings library...something not used with PIVX), this PPA is unlikely to get security updates. However, in the event that one of Ubuntu's 1st party packages used to compile this receives a security update, there are automated notification methods in place.

Support for new (LTS) versions of Ubuntu are added when they are made available on Launchpad for building. Same with support for the riscv64 architecture (which was previously in closed beta, but has now been opened to all PPA's with support starting from Ubuntu Focal 20.04 LTS).

To reiterate: this is a developer/tinkerer resource, and not something that is targeted towards end users

Thanks for the detailed explanation. I think I more fully comprehend the workflow.

[panleone]

utACK fa69949
cannot test since I don't have ubuntu, but should be fine as it is only a change of repository

[Liquid369]

tACK fa69949