Re: Maia Mailgaurd
Hello Janky Jay! -Original Message- Sent: Monday, December 3, 2018 4:17 PM Subject: Re: Maia Mailgaurd Okay. No sweat. I'll work on getting a port patch going as that seems it would be the easiest way to push this out. I'll provide a download as soon as I have something available for testing. Sounds good, thank you for your work on ports! -Reko ___ 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: Maia Mailgaurd
Hello Janky Jay! --Original Message-- Monday, November 26, 2018 10:11 PM Subject: Re: Maia Mailgaurd That being said, with just a few minor changes, I have been able to get Maia to work with PHP 7.2 without any issues (that I've seen, anyway). If you're interested in that, I can provide those changes/patches if you'd like to upgrade to PHP7 before the upstream code is ready. I would also love the preliminary patches for getting Maia to work on PHP7+ Thank you in advance, Reko ___ 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: Upgrade of security/openssl111 fails to install
Longer explanation: DISTVERSION=1.1.1a names the port/package 1.1.1.a which pkg/ports installer understands being older than 1.1.1_2 PORTVERSION=1.1.1a does naming correctly to 1.1.1a which is uderstood as more recent than 1.1.1_2.[1] This is what I did based on reading port naming from porters handbook and changing DIST to PORT. -Reko [1] https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-naming.html -Original Message- From: Reko Turja via freebsd-ports Sent: Wednesday, November 21, 2018 9:17 PM To: po...@freebsd.org Subject: Re: Upgrade of security/openssl111 fails to install Editing the makefile and removing DISTVERSION line and replacing it with: PORTVERSION=1.1.1a fixed the issue for me. -Reko -Original Message- From: j...@mailman-hosting.com Sent: Wednesday, November 21, 2018 5:53 PM To: po...@freebsd.org Subject: Upgrade of security/openssl111 fails to install Hello, After upgrading my packages with poudriere, the updated version (1.1.1.a) is not installed by pkg(8). Apparently, because of the versioning, it's seen as a downgrade: root@teresa:~ # pkg upgrade Updating poudriere-php56-openssl111 repository catalogue... poudriere-php56-openssl111 repository is up to date. All repositories are up to date. Checking for upgrades (1 candidates): 100% Processing candidates (1 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. root@teresa:~ # pkg upgrade -f openssl111 Updating poudriere-php56-openssl111 repository catalogue... poudriere-php56-openssl111 repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) The following 1 package(s) will be affected (of 0 checked): Installed packages to be DOWNGRADED: openssl111: 1.1.1_2 -> 1.1.1.a [poudriere-php56-openssl111] Number of packages to be downgraded: 1 Proceed with this action? [Y/n]: ___ 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: Upgrade of security/openssl111 fails to install
Editing the makefile and removing DISTVERSION line and replacing it with: PORTVERSION=1.1.1a fixed the issue for me. -Reko -Original Message- From: j...@mailman-hosting.com Sent: Wednesday, November 21, 2018 5:53 PM To: po...@freebsd.org Subject: Upgrade of security/openssl111 fails to install Hello, After upgrading my packages with poudriere, the updated version (1.1.1.a) is not installed by pkg(8). Apparently, because of the versioning, it's seen as a downgrade: root@teresa:~ # pkg upgrade Updating poudriere-php56-openssl111 repository catalogue... poudriere-php56-openssl111 repository is up to date. All repositories are up to date. Checking for upgrades (1 candidates): 100% Processing candidates (1 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. root@teresa:~ # pkg upgrade -f openssl111 Updating poudriere-php56-openssl111 repository catalogue... poudriere-php56-openssl111 repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) The following 1 package(s) will be affected (of 0 checked): Installed packages to be DOWNGRADED: openssl111: 1.1.1_2 -> 1.1.1.a [poudriere-php56-openssl111] Number of packages to be downgraded: 1 Proceed with this action? [Y/n]: ___ 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: Poudriere building far more ports than it should
First of all, big thanks to everyone who tried to help! Mostly asking to make sure if this is something to be expected, glitch in some ports or possibly a bug. I think Poudriere pulls in all the possible dependencies, just in case and compiles them as well, just in case. Now I've done some installs etc, I'm just going to blacklist the unnecessary ports which aren't used or linked, in order to make the Poudriere build process meaner and leaner. -Reko ___ 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: Poudriere building far more ports than it should
-Original Message- From: AlexandreC. Guimarães Sent: Wednesday, November 14, 2018 9:26 PM Do you mean the OPTIONS you previously set were not honoured by poudriere? Just in case, poudriere does not `read` OPTIONS and/or other things like make.conf from the default location but from /usr/local/etc/poudriere.d/* Yes, I copied over my make.conf, my src.conf and then /var/db/ports/ to options. And as I said in previous then douplechecked with "poudriere options -c..." What I can understand is that poudriere brought for example every single Imagick dependency, even if I just use a selected few. Of course if everything is as intended and the packages install without any extra dependencies I don't need, I'm happy. Just haven't got time yet to check if the packages I've built "behave", been too busy rebuilding my home firewall/gateway to incorporate the delivery of the packages to intended targets :) Mostly asking to make sure if this is something to be expected, glitch in some ports or possibly a bug. -Reko ___ 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: Poudriere building far more ports than it should
-Original Message- From: Matthias Fechner Sent: Wednesday, November 14, 2018 9:10 PM Am 14.11.2018 um 19:57 schrieb Reko Turja via freebsd-ports: I guess one option would be blacklisting in poudriere those unneeded dependencies which shouldn't be linked with my packages, if my options are honoured by poudriere. have you made your options (maybe they are located on /var/db/ports) available to poudriere? < (normally poudriere searches them in /usr/local/etc/poudriere.d/options) Yes I have andd after noticing the huge increase in ports to be build, doublechecked that my options had really transferred over using poudriere options -c -j -f instead of -C... -Reko ___ 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: Poudriere building far more ports than it should
Hello! -Original Message- From: Dmytro Bilokha On Wed, Nov 14, 2018 at 03:33:38AM +0200, reko.turja--- via freebsd-ports wrote: I finally took the hurdle and made a poudriere VM for building my ports instead of building them on target system. At first I did however build every single port I will need on the VM resulting on 240 or so ports. Then I copied over my options, and the list of installed ports etc. and started the build. For some reason poudriere wants to build a ton of extra baggage (360+ ports instead of 240.) Hello, Reko! Poudriere builds different kinds of ports: 1. Ports from your list. 2. Run-time dependencies of ports from your list. 3. Build-time dependecies of ports from your list. < 4. Run-time and build-time dependencies of your ports dependencies, as well That all I know - Ive been using ports and only ports since early 2000's. So the problem is that I made a dry run from ports, linking only to stuff that I wanted on the final package receiver. Then I copied the list of ports over to poudriere using portversion -oQ. When I started the run, there was suddenly every single dependency I previously dropped brought in. (I know about automake, autoconf and similar build dependencies.) I guess one option would be blacklisting in poudriere those unneeded dependencies which shouldn't be linked with my packages, if my options are honoured by poudriere. -Reko ___ 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: Is there a way to automatically edit port Makefile and plist after updates
-Original Message-
From: Walter Schwarzenfeld
once more for clear, there are some typos
you can for example put in the makefile
.if ${.CURDIR:M*/ports/lang/php56}
CONFIGURE_ARGS+=--disable-mysqlnd
.endif
Thanks a lot Walter!
This does indeed do the trick for my needs - I did a full build test
and reinstall and it worked as it should.
-Reko
___
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: Is there a way to automatically edit port Makefile and plist after updates
-Original Message- From: Chris H There is one port that has completely unneeded things in both Makefile and plist. Is there a way to Automatically change those afterwards - I guess usual method of patching isn't applicable? Of course doing a portsnap fetch update and sedding the unneeded stuff out from a shellscript each night instead of just portsnap is always an option if there's nothing more refined available. If I'm following you correctly; Wouldn't just filing a pr(1) (https://bugs.freebsd.org/bugzilla/) against the port, with your proposed patch, do it? i don't think that even a patch would help at all, as the maintainer closed a PR already with "working as intended" reply. Just can't understand how having runtime module compiled and loaded for toy... - sorry - mysql is "as intended" for us running something else as the favoured datastore. -Reko ___ 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"
Is there a way to automatically edit port Makefile and plist after updates
There is one port that has completely unneeded things in both Makefile and plist. Is there a way to Automatically change those afterwards - I guess usual method of patching isn't applicable? Of course doing a portsnap fetch update and sedding the unneeded stuff out from a shellscript each night instead of just portsnap is always an option if there's nothing more refined available. -Reko ___ 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"
