On Sat, May 1, 2021 at 11:49 PM Theo Buehler <[email protected]> wrote:

> This bundles the sources of ruby-openssl into a package, so we can run a
> regression test from regress/lib/libssl. This gives us a decent amount
> of additional coverage and should help jeremy@ to avoid having to hunt
> down whatever changes trigger regress failures.
>
> I will need some help with the following 2-3 things:
>
> The port uses the ruby module to pull in the default ruby as an RDEP
> (which is needed for the regress test). I assume that this package will
> need some more magic in its Makefile and possibly the PLIST to change
> its name to ruby27-openssl-tests to ensure this works smoothly when the
> default ruby changes. I do not know how to do this correctly.
>
> The name as it currently is triggers a quirk
> Obsolete package: ruby-openssl-tests-20210417 (no longer maintained
> upstream)
> I expect this to be resolved together with the previous point.
>

I think we can avoid this by renaming the port to openssl-ruby-tests.  That
way the package name doesn't change between versions.  Using ruby27-* and
ruby30-* for this is a bad idea, because the packages conflict (unlike
normal ruby27-* and ruby30-* packages).


> The do-install step uses pax. Is there a standard idiom to exclude .orig
> files in subdirectories or is it easier to just ignore them and let
> update-plist whine when doing its job?
>

 Not sure if there is a standard idiom, but using the following pax option
may work: -s /^.*\.orig$//

That should make it so .orig files are not considered as part of the
archive.

OK jeremy@ for import if those changes are OK with you.

Thanks,
Jeremy

Reply via email to