Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x
06.05.2021 10:49, Dima Panov wrote: > Chris, your suggestion leads to dll hell due to mix-links between ssl > libraries :( > At least, your setup easily face up situation where one lib will be built > with “port openss” and consumers still get a “base openssl”. > DEFAULT_VERSION here is set to avoid a such situation — the whole ports > collection should be linked with ONE ssl/crypto library. I disagree. There is no reason for "leaf" ports to depend on ports version of openssl and this is impossible in come cases. For example, net/mpd5 port that links with base libfetch that links with base openssl. So, net/mpd5 must NOT be linked with ports openssl and frankly, it needs not. Global inflexible knob for whole ports tree is bad thing. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: looking for port origin for executable
Piotr Smyrak wrote on 2021/05/05 02:28: > $ find /usr/ports -name pkg-plist | xargs grep -l bin/g-ir-scanner If grep is to be used, then grep -rn --include \*/Makefile\* --include \*/pkg-plist\* -e g-ir-scanner /usr/ports It can also be picked up to some extent from PLIST_FILES in the Makefile. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x
On 2021-05-05 20:49, Dima Panov wrote:
Moin!
Chris, your suggestion leads to dll hell due to mix-links between ssl
libraries :(
At least, your setup easily face up situation where one lib will be built
with
“port openss” and consumers still get a “base openssl”. DEFAULT_VERSION here
is
set to avoid a such situation — the whole ports collection should be linked
with
ONE ssl/crypto library.
I agree. After posting my proposed solution. I was finally able to find
_which_ of
the ports I did it in. Fortunately, it was an isolated case. Which got me to
thinking
that _this_ case here had far reaching ramifications. I would have withdrawn
my
suggestion. But you beat me to it. ;-)
Thanks for the reply (and correction), Dima!
--Chris
--
Dima. (desktop, kde, x11, office, ports-secteam)@FreeBSD team
(flu...@freebsd.org, https://t.me/dima_panov)
On Thursday, May 06, 2021 at 6:26 AM, Chris (mailto:portmas...@bsdforge.com)> wrote:
On 2021-05-05 09:10, Yasuhiro Kimura wrote:
> From: Chris
> Subject: Re: Making a port to use OpenSSL of ports collection on FreeBSD
> 11.x
> Date: Wed, 05 May 2021 08:03:00 -0700
>
> > I ran into a similar situation requiring freebsd 11 users not use
> > SSL from base, and I simply used a conditional based against freebsd
> > version, that also included a RUN_DEPENDS on security/openssl
> > Wouldn't that work in your case?
> >
> > --Chris
>
> Probably only adding security/openssl to *_DEPENDS isn't enough. If
> you look at Mk/Uses/ssl.mk, you'll find the path of include files and
> libraries are customized depending on which ssl stack is used. So you
> also need to add similar custimizetion in Makefile of port avoding
> conflicts with the settings in Mk/Uses/ssl.mk. And it must be hard
> job.
Well unless something has changed significantly in that regard over
the last couple mos. I found it was enough to trap ${OSREL:R} targeting
11 && within that conditional add ssl=openssl
It worked a treat. You may find some additional clues in
bsd.default-versions.mk
HTH
--Chris
>
> ---
> Yasuhiro Kimura
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: looking for port origin for executable
05.05.2021 0:28, Piotr Smyrak wrote: >> Would some kind soul please tell me which port installs the >> executable "g-ir-scanner"? I was purging unused ports and seem to >> have done this one by mistake. > > When I hit a wall like this, this is my usual way to get around without > any additional tools: > > $ find /usr/ports -name pkg-plist | xargs grep -l bin/g-ir-scanner Or just: locale g-ir-scanner Which is much faster as it uses indexed /var/db/locate.database ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x
Moin!
Chris, your suggestion leads to dll hell due to mix-links between ssl libraries
:(
At least, your setup easily face up situation where one lib will be built with
“port openss” and consumers still get a “base openssl”. DEFAULT_VERSION here is
set to avoid a such situation — the whole ports collection should be linked
with ONE ssl/crypto library.
--
Dima. (desktop, kde, x11, office, ports-secteam)@FreeBSD team
(flu...@freebsd.org, https://t.me/dima_panov)
> On Thursday, May 06, 2021 at 6:26 AM, Chris (mailto:portmas...@bsdforge.com)> wrote:
> On 2021-05-05 09:10, Yasuhiro Kimura wrote:
> > From: Chris
> > Subject: Re: Making a port to use OpenSSL of ports collection on FreeBSD
> > 11.x
> > Date: Wed, 05 May 2021 08:03:00 -0700
> >
> > > I ran into a similar situation requiring freebsd 11 users not use
> > > SSL from base, and I simply used a conditional based against freebsd
> > > version, that also included a RUN_DEPENDS on security/openssl
> > > Wouldn't that work in your case?
> > >
> > > --Chris
> >
> > Probably only adding security/openssl to *_DEPENDS isn't enough. If
> > you look at Mk/Uses/ssl.mk, you'll find the path of include files and
> > libraries are customized depending on which ssl stack is used. So you
> > also need to add similar custimizetion in Makefile of port avoding
> > conflicts with the settings in Mk/Uses/ssl.mk. And it must be hard
> > job.
> Well unless something has changed significantly in that regard over
> the last couple mos. I found it was enough to trap ${OSREL:R} targeting
> 11 && within that conditional add ssl=openssl
> It worked a treat. You may find some additional clues in
> bsd.default-versions.mk
>
> HTH
>
> --Chris
> >
> > ---
> > Yasuhiro Kimura
> > ___
> > freebsd-ports@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
signature.asc
Description: PGP signature
Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x
On 2021-05-05 09:10, Yasuhiro Kimura wrote:
From: Chris
Subject: Re: Making a port to use OpenSSL of ports collection on FreeBSD
11.x
Date: Wed, 05 May 2021 08:03:00 -0700
I ran into a similar situation requiring freebsd 11 users not use
SSL from base, and I simply used a conditional based against freebsd
version, that also included a RUN_DEPENDS on security/openssl
Wouldn't that work in your case?
--Chris
Probably only adding security/openssl to *_DEPENDS isn't enough. If
you look at Mk/Uses/ssl.mk, you'll find the path of include files and
libraries are customized depending on which ssl stack is used. So you
also need to add similar custimizetion in Makefile of port avoding
conflicts with the settings in Mk/Uses/ssl.mk. And it must be hard
job.
Well unless something has changed significantly in that regard over
the last couple mos. I found it was enough to trap ${OSREL:R} targeting
11 && within that conditional add ssl=openssl
It worked a treat. You may find some additional clues in
bsd.default-versions.mk
HTH
--Chris
---
Yasuhiro Kimura
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: looking for port origin for executable
> On 5. May 2021, at 20:25, Christian Weisgerber wrote: > > On 2021-05-04, Robert Huff wrote: > >>Would some kind soul please tell me which port installs the >> executable "g-ir-scanner"? I was purging unused ports and seem to >> have done this one by mistake. > > pkg-which(1) > > $ pkg which /usr/local/bin/g-ir-scanner > /usr/local/bin/g-ir-scanner was installed by package > gobject-introspection-1.66.1,1 > This only works if the package it came from is still installed. Robert was trying to find the package that will give him that file, as he deleted that package by accident. Best Michael > -- > Christian "naddy" Weisgerber na...@mips.inka.de > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x
> On 5. May 2021, at 18:56, Stefan Esser wrote:
>
> Am 05.05.21 um 18:00 schrieb Yasuhiro Kimura:
>> You misunderstand my intention. What I would like to do is to make a
>> port use security/openssl instead of base OpenSSL even if user sets
>> 'DEFAULT_VERSIONS+=ssl=base' in /etc/make.conf (or user doesn't
>> customize setting about ssl at all).
Stefan‘s suggestion is AFAIK the best we can do.
mail/opensmtpd has an example of that, but it still requires the user to
actively select the OpenSSL library (mixing OpenSSL libraries in a package set
is problematic).
Best,
Michael
>
> You can mark the port as broken if the user has selected "base" and
> this is incompatible with the port's requirements. E.g.:
>
> .include
>
> .if ${SSL_DEFAULT} == base
> BROKEN_FreeBSD_11= OpenSSL 1.1 required
> .endif
>
> .include
>
> You can of course add a better message, and the user can decide to
> try the compilation again after changing the default. But this will
> of course prevent the building of official packages for FreeBSD-11.
>
>> As I wrote previous mail, if 'USES=python:3.8+' is specified in
>> Makefile of a port, lang/python38 is used for the port event if user
>> adds 'DEFAULT_VERSIONS+=python=3.7' in /etc/make.conf. I'm looking for
>> similar way about ssl setting.
>
> You could add a dependency on the openssl port and make sure, that
> the port's include file and library is used in preference of the
> base version on FreeBSD-11.
>
> But you have to consider the risk of mixing references to the base and
> the ports version in one binary (e.g. other libraries are linked in that
> had been built against the base version).
>
> Regards, STefan
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: looking for port origin for executable
On 2021-05-04, Robert Huff wrote: > Would some kind soul please tell me which port installs the > executable "g-ir-scanner"? I was purging unused ports and seem to > have done this one by mistake. pkg-which(1) $ pkg which /usr/local/bin/g-ir-scanner /usr/local/bin/g-ir-scanner was installed by package gobject-introspection-1.66.1,1 -- Christian "naddy" Weisgerber na...@mips.inka.de ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x
Am 05.05.21 um 18:00 schrieb Yasuhiro Kimura:
> You misunderstand my intention. What I would like to do is to make a
> port use security/openssl instead of base OpenSSL even if user sets
> 'DEFAULT_VERSIONS+=ssl=base' in /etc/make.conf (or user doesn't
> customize setting about ssl at all).
You can mark the port as broken if the user has selected "base" and
this is incompatible with the port's requirements. E.g.:
.include
.if ${SSL_DEFAULT} == base
BROKEN_FreeBSD_11= OpenSSL 1.1 required
.endif
.include
You can of course add a better message, and the user can decide to
try the compilation again after changing the default. But this will
of course prevent the building of official packages for FreeBSD-11.
> As I wrote previous mail, if 'USES=python:3.8+' is specified in
> Makefile of a port, lang/python38 is used for the port event if user
> adds 'DEFAULT_VERSIONS+=python=3.7' in /etc/make.conf. I'm looking for
> similar way about ssl setting.
You could add a dependency on the openssl port and make sure, that
the port's include file and library is used in preference of the
base version on FreeBSD-11.
But you have to consider the risk of mixing references to the base and
the ports version in one binary (e.g. other libraries are linked in that
had been built against the base version).
Regards, STefan
OpenPGP_signature
Description: OpenPGP digital signature
Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x
From: Chris Subject: Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x Date: Wed, 05 May 2021 08:03:00 -0700 > I ran into a similar situation requiring freebsd 11 users not use > SSL from base, and I simply used a conditional based against freebsd > version, that also included a RUN_DEPENDS on security/openssl > Wouldn't that work in your case? > > --Chris Probably only adding security/openssl to *_DEPENDS isn't enough. If you look at Mk/Uses/ssl.mk, you'll find the path of include files and libraries are customized depending on which ssl stack is used. So you also need to add similar custimizetion in Makefile of port avoding conflicts with the settings in Mk/Uses/ssl.mk. And it must be hard job. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x
From: Michael Gmelin Subject: Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x Date: Wed, 5 May 2021 17:32:02 +0200 > Which port are you talking about by the way? > > This worked for me just fine in the past (placed in make.conf): > > DEFAULT_VERSIONS+=ssl=libressl > > for LibreSSL and > > DEFAULT_VERSIONS+=ssl=openssl > > for openssl from ports. > > See also: > > $ head -n12 /usr/ports/Mk/Uses/ssl.mk > # Handle dependency on *ssl ports. > # > # Feature: SSL_DEFAULT > # Usage:USES=ssl > # Valid ARGS: none (build and run), build, run > # > # The user can choose which ssl library he wants with: > # > # DEFAULT_VERSIONS+=ssl= > # > # Variants being base, openssl, libressl, and libressl-devel. > # > > Cheers, > Michael You misunderstand my intention. What I would like to do is to make a port use security/openssl instead of base OpenSSL even if user sets 'DEFAULT_VERSIONS+=ssl=base' in /etc/make.conf (or user doesn't customize setting about ssl at all). As I wrote previous mail, if 'USES=python:3.8+' is specified in Makefile of a port, lang/python38 is used for the port event if user adds 'DEFAULT_VERSIONS+=python=3.7' in /etc/make.conf. I'm looking for similar way about ssl setting. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x
On Wed, 05 May 2021 23:22:08 +0900 (JST) Yasuhiro Kimura wrote: > From: Michael Gmelin > Subject: Re: Making a port to use OpenSSL of ports collection on > FreeBSD 11.x Date: Tue, 4 May 2021 23:05:06 +0200 > > > See > > https://docs.freebsd.org/en/books/porters-handbook/uses/#uses-ssl > > > > Best > > I checked it but couldn't find proper solution. > > I think what is necessary in my case is something like version-spec > argument of 'USES=python'. > > For example, if 'USES=python:3.8+' is specified in Makefile of a port, > lang/python38 is used for it even if user sets > 'DEFAULT_VERSIONS+=python=3.7' in /etc/make.conf. > > But 'USES=ssl' doesn't provide such argument. Which port are you talking about by the way? This worked for me just fine in the past (placed in make.conf): DEFAULT_VERSIONS+=ssl=libressl for LibreSSL and DEFAULT_VERSIONS+=ssl=openssl for openssl from ports. See also: $ head -n12 /usr/ports/Mk/Uses/ssl.mk # Handle dependency on *ssl ports. # # Feature: SSL_DEFAULT # Usage:USES=ssl # Valid ARGS: none (build and run), build, run # # The user can choose which ssl library he wants with: # # DEFAULT_VERSIONS+=ssl= # # Variants being base, openssl, libressl, and libressl-devel. # Cheers, Michael > > --- > Yasuhiro Kimura > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to > "freebsd-ports-unsubscr...@freebsd.org" -- Michael Gmelin ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x
On 2021-05-05 07:22, Yasuhiro Kimura wrote: From: Michael Gmelin Subject: Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x Date: Tue, 4 May 2021 23:05:06 +0200 See https://docs.freebsd.org/en/books/porters-handbook/uses/#uses-ssl Best I checked it but couldn't find proper solution. I think what is necessary in my case is something like version-spec argument of 'USES=python'. For example, if 'USES=python:3.8+' is specified in Makefile of a port, lang/python38 is used for it even if user sets 'DEFAULT_VERSIONS+=python=3.7' in /etc/make.conf. But 'USES=ssl' doesn't provide such argument. I ran into a similar situation requiring freebsd 11 users not use SSL from base, and I simply used a conditional based against freebsd version, that also included a RUN_DEPENDS on security/openssl Wouldn't that work in your case? --Chris --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x
From: Michael Gmelin Subject: Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x Date: Tue, 4 May 2021 23:05:06 +0200 > See https://docs.freebsd.org/en/books/porters-handbook/uses/#uses-ssl > > Best I checked it but couldn't find proper solution. I think what is necessary in my case is something like version-spec argument of 'USES=python'. For example, if 'USES=python:3.8+' is specified in Makefile of a port, lang/python38 is used for it even if user sets 'DEFAULT_VERSIONS+=python=3.7' in /etc/make.conf. But 'USES=ssl' doesn't provide such argument. --- Yasuhiro Kimura ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ lang/clojure-mode.el| 5.11.0 | 5.13.0 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Reported by:portscout! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
looking for committer
Hi, I'm looking for a committer for the following port issues. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255118 (mongodb40, maintainer gave +feedback instead of +approval) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255117 (monbodb40-tools, maintainer gave +feedback instead of +approval) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255255 (grafana7 depends on ca_root_nss, maintainer did not react for 2 weeks) Thanks in advance. Regards, Ronald. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
