Gleb Popov <[email protected]> writes:

On Tue, Feb 24, 2026 at 3:51 PM Markus Graf <[email protected]> wrote:

It sounds like you did an impressive work.

Thank you!

Testing

That's right, poudriere testport does not do that (yet). But you can make Ports framework run tests as part of the build by defining WITH_TESTING=yes or
WITH_TESTING_PORTS=your/port1 your/port2
in make.conf. In Poudriere context this config is located in
/usr/local/etc/poudriere.d

Put tests under the do-test target and its dependencies under TEST_DEPENDS. Do not force users to always run tests during the build - currently this is an
optional feature and is guarded behind WITH_TESTING knob.

OK, thank you!

Stubs

I'm not a Java expert, so not sure what's being talked about here.
But there is a BINARY_ALIAS knob that can be used to create
stub executables, you might find it useful.

I will look into that.


What's the problem in properly wiring in those dependencies?
Are they heavyweight or not ported yet?

One, slf4j, is ported, OSGi is not ported.

I do not think a library should force a choice of logging framework on you. That should be the applications choice.

I do not want to needlessly replicate the location of jar files since it will be hard to debug dependencies. The infamous classpath.

I see these main valid reasons to put jar files into FreeBSD ports:
1. they contain or are tied to native code.
2. having the ports infrastructure run the tests so we know when something breaks. 3. they are a standalone applications, maybe even startable via service start. 4. they need to be patched to run on FreeBSD or profit from customization.

The main reason to make a port of JavaCPP instead of just using the upstream jar was to have the tests. Also to have an official FreeBSD capable jar before upstream cut a new release two days ago.

I suspect your patch would be lengthy, so I'd recommend you to
put your ports onto our Phabricator [1] or make a pull request
on GitHub [2]. Get me (@arrowd) on the hook and I will provide
a review.

[1] https://reviews.freebsd.org/
[2] https://github.com/freebsd/freebsd-ports

Is one PR on github ok or should I submit one per port?

Once I am clear about the FreeBSD ports I will try to get one other PR into dtlnative upstream before I send PR to you.

Thank you!

--
Markus Graf

Tel.: +49 172 840 26 08
Email: [email protected]


Reply via email to