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 +-+ devel/lua-sysctl| 1.0 | v1.1 +-+ 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: openntpd-5.7p4_2,2 depends on libressl-2.2.6 ?!
On Thu 2016-03-10 (19:17), Walter Schwarzenfeld wrote:
> Makefile
> OPTIONS_DEFAULT=RESSL
>
> RESSL_LIB_DEPENDS= libtls.so:${PORTSDIR}/security/libressl
>
>
> turn option RESSL to off.
I guess this is because it's a few months later but these lines are no
longer in the Makefile? (/usr/ports/net/openntpd/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: Welcome to our new portmgr members
Congratulations to them! \0/ and to our community for having them ;) ___ 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: HEADSUP: FLAVORS (initial version) and subpackages proposals
> On 23 Dec 2016, at 10:34 AM, Miroslav Lachman <000.f...@quip.cz> wrote: > > But we don't have that now. For example dns/py-dnspython can create > py27-dnspython, py33-dnspython, py34-dnspython, py35-dnspython - four > different packages from one origin, one Makefile. Noticed that too. This could be easily solved with slave ports that set this for e.g. py27-dnspython: USES= python:2.7 and in the master port USES?= python USES+= other-uses-stuff In fact, py-dnspython master port already does it this way. But most Python ports do not. Cheers, Franco ___ 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: HEADSUP: FLAVORS (initial version) and subpackages proposals
Baptiste Daroussin wrote on 2016/12/22 21:08: On Mon, Dec 19, 2016 at 07:12:02PM +0100, Miroslav Lachman wrote: Matthew Seaman wrote on 2016/12/19 09:45: On 19/12/2016 07:47, David Demelier wrote: I have been working for a while on 2 long standing feature request for the ports tree: flavors and subpackages. For flavors I would like to propose a simple approach first which is more like a rework of the slave ports for now: Examples available here: https://reviews.freebsd.org/D8840 (with the implementation) and https://reviews.freebsd.org/D8843 Design: introduce a 3rd level in the hierarchy and make it work a bit like slave ports pros: - all slave ports are self hosted under the same directory: easier for maintenance - should work with all existing tools This is what I really wanted for years especially for ports like spell checker. Some are in dedicated categories such as french/aspell while other are in textproc/-aspell and that's a big mess. OpenBSD ports has something like textproc/aspell/ and that is very nice and clean. If the plan is to do the same, that is definitely a major improvement. I really like this idea, although it's going to add a lot of extra directories and very similar small Makefiles to the ports. Every python port would grow flavours to support two major versions of python just for starters, and those additional Makefiles would be almost identical across the python2 flavour and across the python3 flavour. Can this be processed by some code in Mk/bsd.*.mk? I mean if we can add something to the main Makefile then we don't need to add subdirectories and sub-Makefiles for each Python module port. If we do that we do break the paradigm: 1 package = 1 origin which will break portmaster/portupgrade for example But we don't have that now. For example dns/py-dnspython can create py27-dnspython, py33-dnspython, py34-dnspython, py35-dnspython - four different packages from one origin, one Makefile. OK, I noticed now that slave port for py3 was added "recently" but even this slave port can create 3 different packages according to what default version of python 3 is installed. Another thing is that portmaster and portupgrade are not well maintained and I think ports / ports framework evolution should not be slowed down because of "3rd party" utilities. Or we will end up with adding tons of directories and small files just to create endless pile of slave ports. Miroslav Lachman ___ 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"
any PRs waiting for a commiter
I have a lof of PRs to Commit: Maintainer timeout: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214323 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214341 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214354 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214872 Ready for commit: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214260 Thx Jochen ___ 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"
