Re: Packaging 42.3.0 for MacPorts -- need some clarifications
| От | Georges Martin |
|---|---|
| Тема | Re: Packaging 42.3.0 for MacPorts -- need some clarifications |
| Дата | |
| Msg-id | 0F6676E3-474F-4C63-ADED-C3A3FAB3FF9D@gmail.com обсуждение исходный текст |
| Ответ на | Re: Packaging 42.3.0 for MacPorts -- need some clarifications (Vladimir Sitnikov <sitnikov.vladimir@gmail.com>) |
| Список | pgsql-jdbc |
Thanks, Vladimir, this helps a lot understanding the Maven/Gradle situation.
There are several ways to build and package pgjdbc:a) Build from Git sources. That requires Gradle, and it enables running more tests, so you have better confidence in the resulting artifactb) Build from "source release" (see -jdbc-src.tar.gz https://repo1.maven.org/maven2/org/postgresql/postgresql/42.3.0/ ). Those are simplified sources,and the purpose is to add convenience for cases like Debian that lack Gradle. The set of tests and features is reduced, however, the driver should still work in most cases.
I already have a 42.3.0 Portfile reverting back to Maven builds using source release but, as I would like to add tests to the Portfile in the future, I think I'll switch to Git sources and stay with Gradle builds.
c) You could grab the official release artifacts from https://repo1.maven.org/maven2/org/postgresql/postgresql/
For instance, Gradle port of MacPorts grabs Gradle from the official distribution site, and it does not build Gradle from sources: https://github.com/macports/macports-ports/blob/cb0311519f9752e4507cf64ba042045690ac429a/devel/gradle/Portfile#L23-L29
You are right: some large codebase like JDK are indeed using upstream binaries, but pgjdbc is not that large... :-) Here, I think I'll stay old school and limit potential "supply chain" issues ;-)
Thanks again :-)
Georges
В списке pgsql-jdbc по дате отправления: