Re: FLAVOR for Qt4 and Qt5 (was Re: Flavor or not for this port?)
Hi Loïc,
Am 04.01.2018 um 18:37 schrieb L.Bartoletti:
> Hi Mathieu,
>
> Thank you for your review and tips.
>
> I have just submitted the patch.
>
> Rainer, QGis 2 may be able to use Qwt6 instead of Qwt5?
I just tried to use Qwt6 with QGIS2 and it seems to work. A few small
tests showed no regressions, so far.
If this is true, I could change my port to use qwt6@qt4, once flavors
for QWT hit the ports tree.
Thanks to both, Loïc and Mathieu, for the work on this.
Best wishes,
Rainer
>
> Regards.
>
> Loïc
>
> On 21.12.2017 17:10, Mathieu Arnold wrote:
>> Le 19/12/2017 à 20:48, L.Bartoletti a écrit :
>>> Hi,
>>>
>>> Here's my WIP
>>>
>>> https://gitlab.com/lbartoletti/freebsd_ports/tree/master/qwt6
>> As long as you are defining a default FLAVOR value, do it right:
>>
>> FLAVOR?= ${FLAVORS:[1]}
>>
>> There are a few stuffs that could be simplified, this works for both
>> flavors:|
>>
>> |
>>
>> |PLIST= ${PKGDIR}/pkg-plist.${FLAVOR} PLIST_SUB+=
>> QT_MKSPECDIR=lib/${FLAVOR}/mkspecs DOCSDIR=
>> ${PREFIX}/share/doc/qwt6-${FLAVOR} And this: ||@${REINPLACE_CMD} -e
>> 's/__QT_VERSION__/${FLAVOR:S/qt//}/g'
>> ${WRKSRC}/qwtconfig.pri|
>> ||
>>
>>
>>
>> You are missing:
>>
>> qt4_CONFLICTS_INSTALL= qwt6-qt5
>> qt5_CONFLICTS_INSTALL= qwt6-qt4
>>
>>
>>
>
___
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: FLAVOR for Qt4 and Qt5 (was Re: Flavor or not for this port?)
Hi Loïc,
Am 04.01.2018 um 18:37 schrieb L.Bartoletti:
> Hi Mathieu,
>
> Thank you for your review and tips.
>
> I have just submitted the patch.
>
> Rainer, QGis 2 may be able to use Qwt6 instead of Qwt5?
I just tried to use Qwt6 with QGIS2 and it seems to work. A few small
tests showed no regressions, so far.
If this is true, I could change my port to use qwt6@qt4, once flavors
for QWT hit the ports tree.
Thanks to both, Loïc and Mathieu, for the work on this.
Best wishes,
Rainer
>
> Regards.
>
> Loïc
>
> On 21.12.2017 17:10, Mathieu Arnold wrote:
>> Le 19/12/2017 à 20:48, L.Bartoletti a écrit :
>>> Hi,
>>>
>>> Here's my WIP
>>>
>>> https://gitlab.com/lbartoletti/freebsd_ports/tree/master/qwt6
>> As long as you are defining a default FLAVOR value, do it right:
>>
>> FLAVOR?= ${FLAVORS:[1]}
>>
>> There are a few stuffs that could be simplified, this works for both
>> flavors:|
>>
>> |
>>
>> |PLIST= ${PKGDIR}/pkg-plist.${FLAVOR} PLIST_SUB+=
>> QT_MKSPECDIR=lib/${FLAVOR}/mkspecs DOCSDIR=
>> ${PREFIX}/share/doc/qwt6-${FLAVOR} And this: ||@${REINPLACE_CMD} -e
>> 's/__QT_VERSION__/${FLAVOR:S/qt//}/g'
>> ${WRKSRC}/qwtconfig.pri|
>> ||
>>
>>
>>
>> You are missing:
>>
>> qt4_CONFLICTS_INSTALL= qwt6-qt5
>> qt5_CONFLICTS_INSTALL= qwt6-qt4
>>
>>
>>
>
___
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: using security/openssl in a port
Le 05/01/2018 à 03:11, Matthew Luckie a écrit :
> Hi,
>
> I maintain a port that has a new release which requires openssl 1.0.2 to
> build. FreeBSD 10.3 and 10.4 both have openssl 1.0.1, and 11 onwards
> have 1.0.2. Is there a magic way to have this port depend on ports
> openssl for freebsd releases without openssl 1.0.2? I ran
>
> find /usr/ports -exec grep "security/openssl" {} \; -print
>
> and didn't find anything that I could use as a recipe. USES = ssl
> doesn't seem to be it either.
You NEVER forcefully depend on security/openssl directly. You USES=ssl,
and you use whatever default is available. So, in your case, you need
something like this:
.include
.if ${OSVERSION} < 1100085
BROKEN_SSL= base
BROKEN_SSL_REASON= Needs OpenSSL 1.0.2+
.endif
--
Mathieu Arnold
signature.asc
Description: OpenPGP digital signature
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 +-+ games/freedoko | 0.7.16 | 0.7.17 +-+ 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 Thanks. ___ 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: using security/openssl in a port
05.01.2018 11:16, Matthew Luckie пишет:
> On 1/5/18 5:09 PM, Eugene Grosbein wrote:
>> On 05.01.2018 09:44, Matthew Luckie wrote:
>>
>>> My main worry is that I could not find a single port that apparently
>>> depends on security/openssl. I'm worried that its more complicated than
>>> simply declaring a dependency on security/openssl on particular freebsd
>>> versions because other ports that use openssl might link against it
>>> without registering a dependency. Is my worry misplaced?
>>
>> Why don't you read the Porter's Handbook? It has answers to all your
>> questions:
>>
>> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/uses-ssl.html
>
> I already said that I considered USES = ssl and that it didn't seem to
> address my concerns. Can you please point me at a port that depends on
> OpenSSL from ports using USES = ssl (or whatever this page of the
> porters handbook is trying to tell me to do).
For example, net/vtun has this:
.include
.if ${SSL_DEFAULT:Mopenssl-devel}
BROKEN= Does not build with openssl-devel
.endif
.include
That is, it stops build if user has specified SSL_DEFAULT=openssl-devel.
You need to stop build if FreeBSD version is old and user has NOT specified
SSL_DEFAULT=openssl (instead of SSL_DEFAULT=base) to build your port with
security/openssl.
signature.asc
Description: OpenPGP digital signature
py27 ports always show "new version available"
I'm sure I caused this problem when FLAVORS came out by trying to set a FLAVOR using "make". Using portmaster as I always have, py27-cffi and py27-setuptools update to the latest version that portsnap downloads but checking for new versions always returns "new version available" even after updating. portmaster -L --index-only | egrep '(ew|ort) version|total install' ===>>> New version available: py27-cffi-1.11.2 ===>>> New version available: py27-setuptools-38.2.5 Trying to remove the port with portmaster, pkg or 'make' and reinstalling does not change anything. FreeBSD 11.1 RELEASE p6 ___ 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: py27 ports always show "new version available"
On Fri, Jan 05, 2018 at 10:50:11AM -0600, Rob Belics wrote: > I'm sure I caused this problem when FLAVORS came out by trying to set a > FLAVOR using "make". Using portmaster as I always have, py27-cffi and > py27-setuptools update to the latest version that portsnap downloads but > checking for new versions always returns "new version available" even after > updating. > > portmaster -L --index-only | egrep '(ew|ort) version|total install' > ===>>> New version available: py27-cffi-1.11.2 > ===>>> New version available: py27-setuptools-38.2.5 > > Trying to remove the port with portmaster, pkg or 'make' and > reinstalling does not change anything. > Saw the same abysmal situation yesterday with devel/flang. The ports system wanted to update py27-enum34-1.1.6 and py27-sphinx-1.4.8_2,1. After 'pkg delete XXX' of the offending ports, portmaster would install the ports, then promptly fail installing devel/flang because new versions were available and installation of new versions failed because, well, the py27-XXX ports were already installed. I had to resort to the good old-fashion 'cd devel/flang; make && make install && make clean' and even this method failed a few attempts. :( -- Steve ___ 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"
Puppet SSL-related problems after updating Ruby
I recently updated packages on a 11.0 machine, which upgraded Ruby from 2.3.5 to 2.3.6 (I think), and my Puppet install broke. It is logging SSL-related issues with this message: SSL_read: decryption failed or bad record mac I thought maybe it was a problem with outdated OpenSSL so I updated to 11.1-R-p6 a minute ago, but the problem persists. I did reinstall all packages after updating and rebooted a few times throughout the process; followed the handbook. $ openssl version;uname -a;freebsd-version OpenSSL 1.0.2k-freebsd 26 Jan 2017 FreeBSD puppet1-test 11.1-RELEASE-p4 FreeBSD 11.1-RELEASE-p4 #0: Tue Nov 14 06:12:40 UTC 2017 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 11.1-RELEASE-p6 I'm not sure what to do at this point. I could force it to reinstall Ruby 2.3.5, and lock those packages, which worked on 11.0, but I would rather be able to keep things up to date. I could possibly try OpenSSL from ports, but is there a way to use that with Puppet from pkg? ___ 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"
