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 +-+ security/teleport | 4.2.8 | v4.2.9 +-+ textproc/coccigrep | 1.19| v1.20 +-+ 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"
Re: Poudriere - Compile ALL Ports
Hello Chris,
thanks for your reply. Thanks for the hint about ports-mgmt/synth. I am
definitly going to have a look into this! Well, my Podriere is using
Jails by default. Is there any hack you applied for this issue to avoid?
Best regards,
Leander
Am 05.05.20 um 22:46 schrieb Chris:
On Tue, 5 May 2020 22:38:36 +0200 Leander Schaefer i...@netocean.de said
Hello,
I have been dealing with Poudriere for quite a while and one of the
most issues I have is, that I have ports which won't compile along
with another. Reason is mostly something like:
pkg-static: ImageMagick7-7.0.10.6 conflicts with
ImageMagick6-6.9.11.6,1 (installs files into the same place).
Problematic file: /usr/local/bin/Magick++-config
So in other words a newer version is going to place its binaries etc.
into the same place as the previous version. I have read and used
something like:
# Build several PHP versions parallel on the same server:
# https://github.com/freebsd/poudriere/issues/602
PHP_ALT=php56 php70 php71 php72 php73
.for port in ${PHP_ALT}
.if ${.CURDIR:M*/ports*/*/${port}*}
DISABLE_CONFLICTS=YES
PREFIX=/usr/local/${port}
PHPBASE=/usr/local/${port}
LOCALBASE=/usr/local
CONFIGURE_ARGS+=--datadir=/usr/local/${port}/share
CONFIGURE_ARGS+=--bindir=/usr/local/${port}/bin
CONFIGURE_ARGS+=--with-config-file-scan-dir=/usr/local/${port}/etc/php
#CONFIGURE_ARGS+=--with-php-config=/usr/local/${port}/bin/php.conf
#CONFIGURE_ARGS+=--with-iconv=/usr/local
#CONFIGURE_ARGS+=--with-pcre-dir=/usr/local
.endif
.endfor
But I was wondering: How is the FreeBSD Team dealing with this, when
they compile their packages for the public repository? Because we
only use one official repository and all packages are there ... some
even with differet options enabled. So how to deal with this? How can
I compile the entire ports tree without issues and build a repository
of it and some packages even with different options? Lets say one
OpenLDAP with SASL and another one with SASL? The only way I was able
to do this was building it in separate repositories.
Thanks
I use Jails which helps weed out some of the conflicts. That is different
jails for different (port) options that *may* cause conflict. Also
ports-mgmt/synth is pretty damn clever about sorting out conflicts.
However, I have no direct knowledge on how the pkg build admins deal with
this. But just thought I'd share some alternate avenue(s) FWIW. :-)
___
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"
Mit freundlichen Grüßen
Leander Schäfer
Logo
NetOcean GmbH
Legienstraße 20
65929 Frankfurt am Main
Contact
Telefon
+49 69 1539 1025
Fax
+49 69 1539 1024
Mobil
+49 160 6916 361
E-Mail
i...@netocean.de
Website
http://NetOcean.de
Re: Poudriere - Compile ALL Ports
On Tue, 5 May 2020 22:38:36 +0200 Leander Schaefer i...@netocean.de said
Hello,
I have been dealing with Poudriere for quite a while and one of the most
issues I have is, that I have ports which won't compile along with
another. Reason is mostly something like:
pkg-static: ImageMagick7-7.0.10.6 conflicts with ImageMagick6-6.9.11.6,1
(installs files into the same place). Problematic file:
/usr/local/bin/Magick++-config
So in other words a newer version is going to place its binaries etc.
into the same place as the previous version. I have read and used
something like:
# Build several PHP versions parallel on the same server:
# https://github.com/freebsd/poudriere/issues/602
PHP_ALT=php56 php70 php71 php72 php73
.for port in ${PHP_ALT}
.if ${.CURDIR:M*/ports*/*/${port}*}
DISABLE_CONFLICTS=YES
PREFIX=/usr/local/${port}
PHPBASE=/usr/local/${port}
LOCALBASE=/usr/local
CONFIGURE_ARGS+=--datadir=/usr/local/${port}/share
CONFIGURE_ARGS+=--bindir=/usr/local/${port}/bin
CONFIGURE_ARGS+=--with-config-file-scan-dir=/usr/local/${port}/etc/php
#CONFIGURE_ARGS+=--with-php-config=/usr/local/${port}/bin/php.conf
#CONFIGURE_ARGS+=--with-iconv=/usr/local
#CONFIGURE_ARGS+=--with-pcre-dir=/usr/local
.endif
.endfor
But I was wondering: How is the FreeBSD Team dealing with this, when
they compile their packages for the public repository? Because we only
use one official repository and all packages are there ... some even
with differet options enabled. So how to deal with this? How can I
compile the entire ports tree without issues and build a repository of
it and some packages even with different options? Lets say one OpenLDAP
with SASL and another one with SASL? The only way I was able to do this
was building it in separate repositories.
Thanks
I use Jails which helps weed out some of the conflicts. That is different
jails for different (port) options that *may* cause conflict. Also
ports-mgmt/synth is pretty damn clever about sorting out conflicts.
However, I have no direct knowledge on how the pkg build admins deal with
this. But just thought I'd share some alternate avenue(s) FWIW. :-)
___
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"
Poudriere - Compile ALL Ports
Hello,
I have been dealing with Poudriere for quite a while and one of the most
issues I have is, that I have ports which won't compile along with
another. Reason is mostly something like:
pkg-static: ImageMagick7-7.0.10.6 conflicts with ImageMagick6-6.9.11.6,1
(installs files into the same place). Problematic file:
/usr/local/bin/Magick++-config
So in other words a newer version is going to place its binaries etc.
into the same place as the previous version. I have read and used
something like:
# Build several PHP versions parallel on the same server:
# https://github.com/freebsd/poudriere/issues/602
PHP_ALT=php56 php70 php71 php72 php73
.for port in ${PHP_ALT}
.if ${.CURDIR:M*/ports*/*/${port}*}
DISABLE_CONFLICTS=YES
PREFIX=/usr/local/${port}
PHPBASE=/usr/local/${port}
LOCALBASE=/usr/local
CONFIGURE_ARGS+=--datadir=/usr/local/${port}/share
CONFIGURE_ARGS+=--bindir=/usr/local/${port}/bin
CONFIGURE_ARGS+=--with-config-file-scan-dir=/usr/local/${port}/etc/php
#CONFIGURE_ARGS+=--with-php-config=/usr/local/${port}/bin/php.conf
#CONFIGURE_ARGS+=--with-iconv=/usr/local
#CONFIGURE_ARGS+=--with-pcre-dir=/usr/local
.endif
.endfor
But I was wondering: How is the FreeBSD Team dealing with this, when
they compile their packages for the public repository? Because we only
use one official repository and all packages are there ... some even
with differet options enabled. So how to deal with this? How can I
compile the entire ports tree without issues and build a repository of
it and some packages even with different options? Lets say one OpenLDAP
with SASL and another one with SASL? The only way I was able to do this
was building it in separate repositories.
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: Out of memory building lang/ghc-8.8.3
Something like this maybe: ALLOW_MAKE_JOBS_PACKAGES="pkg llvm* gcc* node* *webengine rust* firefox* mame mess" >From this Forums post: https://forums.freebsd.org/threads/howto-speeding-up-poudriere-build-times.69431/#post-460170 HTH, Jose On 2020-05-05 04:09, andrew clarke wrote: > On 2020-05-05 14:19:50, Gleb Popov (arr...@freebsd.org) wrote: > >> On Tue, May 5, 2020 at 1:37 PM andrew clarke wrote: >> >>> Beware anyone building lang/ghc-8.8.3 from the ports tree. Building it >>> here on FreeBSD 12.1-REL AMD64 with Poudriere, the build ran out of swap, >>> despite the PC having 8 GB RAM, 8 GB swap and not much else running. >>> >>> My /usr/local/etc/poudriere.conf: >>> >>> BASEFS=/poudriere >>> ZPOOL=zroot >>> FREEBSD_HOST=http://mirror.internode.net/ >>> POUDRIERE_DATA=/poudriere/data >>> RESOLV_CONF=/etc/resolv.conf >>> DISTFILES_CACHE=/usr/ports/distfiles >>> USE_TMPFS=yes >>> ALLOW_MAKE_JOBS=yes >>> KEEP_OLD_PACKAGES=yes >>> PARALLEL_JOBS=8 >>> >>> Maybe I can retune the last three parameters to use less memory. I've not >>> tried yet. >>> >>> This isn't really a whinge, I'm just surprised it failed. I'd have thought >>> 8 GB was enough. >>> >>> (ghc is a build dependency of textproc/hs-pandoc) >>> >> >> Did you have something else building at the same time? >> >> On my laptop with 16 Gb of RAM I also see OOM failures when building >> multiple "heavy" packages (llvmXX, gccX, ghc, rust, libreoffice) >> simultaneously. In this case I use -J poudriere option to limit number of >> jobs. > > Nothing else building. > > This is a headless server, so I've no need to build something the size of > libreoffice or chromium. I've noticed llvm10 takes a long time to build, but > 8 GB seems plenty of memory for it. > > The -J option sounds like the way to go, provided I remember to use it > next time. Or I could instead set PARALLEL_JOBS=1 in poudriere.conf but then > build performance will suffer for every port, which isn't ideal. > > But perhaps there's an option to limit make jobs just for a single port, set > in > /usr/local/etc/poudriere.d/make.conf ? That would be nice. > ___ > 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"
HEADS-UP: /usr/bin/objdump to be removed
I plan to remove the obsolete GNU binutils 2.17.50 objdump from the
base system in the next few days.
If you currently use objdump from the base system you can give
llvm-objdump a try instead - it is mostly compatible, but has a few
missing options and the output format may be slightly different.
Otherwise, install binutils from ports or packages.
There are a few ports that need adjustment as well, identified in
exp-run PR 212319:
- PR 246229 databases/galera
Fixed by adding a ${LOCALBASE}/bin/objdump:devel/binutils BUILD_DEPENDS.
- PR 241159 devel/powerpc64-gcc (and other *-gcc ports)
The build finishes, but "make package" fails because certain files are missing.
- PR 241157: www/node (and node*)
- No PR yet, graphics/embree
Once this is committed the only remaining obsolete binutils tool will
be /usr/bin/as, on amd64 and i386 only. I expect it will also be
removed for FreeBSD 13.0.
___
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: ports: Need new future
Yes, or, at least a notification that defaults have changed. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Tue, May 5, 2020 at 12:13 AM Alex V. Petrov wrote: > Hi All! > > I think that for the ports menu options need a new "default" button > (make rmconfig). > > -- > - > Alex. > ___ > 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: Out of memory building lang/ghc-8.8.3
* Kubilay Kocak [20200505 21:26]:
> On 5/05/2020 9:09 pm, andrew clarke wrote:
> > The -J option sounds like the way to go, provided I remember to use it
> > next time. Or I could instead set PARALLEL_JOBS=1 in poudriere.conf but then
> > build performance will suffer for every port, which isn't ideal.
> >
> > But perhaps there's an option to limit make jobs just for a single port,
> > set in
> > /usr/local/etc/poudriere.d/make.conf ? That would be nice.
Don't confuse poudriere's PARALLEL_JOBS with the number of jobs for
building a single port. Poudriere defaults to always use a single job
for a single port, you can override this with ALLOW_MAKE_JOBS=yes
globally, or with ALLOW_MAKE_JOBS_PACKAGES for individual ports.
PARALLEL_JOBS just tells how many ports are built in parallel.
> This doesn't help for non-OPTIONS variables, but we have this recently
> submitted feature/review:
>
> https://reviews.freebsd.org/D24324
>
> For use like:
>
> devel_llvm80_VARS=DISABLE_MAKE_JOBS=yes
> devel_llvm90_VARS=DISABLE_MAKE_JOBS=yes
>
> This would satisfy this and other per-port specific build options cases.
As long as this isn't available yet, there's always the old trick
checking .CURDIR like for this example:
.if ${.CURDIR:M*/devel/llvm*}
DISABLE_MAKE_JOBS=yes
.endif
This works because make.conf is just included. But see above why this
shouldn't be needed to control the make jobs when using poudriere.
--
Dipl.-Inform. Felix Palmen ,.//..
{web} http://palmen-it.de {jabber} [see email] ,//palmen-it.de
{pgp public key} http://palmen-it.de/pub.txt // """""""""""
{pgp fingerprint} A891 3D55 5F2E 3A74 3965 B997 3EF2 8B0A BC02 DA2A
signature.asc
Description: PGP signature
Re: Out of memory building lang/ghc-8.8.3
## andrew clarke (m...@ozzmosis.com): > But perhaps there's an option to limit make jobs just for a single port, set > in > /usr/local/etc/poudriere.d/make.conf ? That would be nice. echo "DISABLE_MAKE_JOBS=yes" >> lang/ghc/Makefile.local Regards, Christoph -- Spare Space ___ 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: Out of memory building lang/ghc-8.8.3
On 5/05/2020 9:09 pm, andrew clarke wrote:
On 2020-05-05 14:19:50, Gleb Popov (arr...@freebsd.org) wrote:
On Tue, May 5, 2020 at 1:37 PM andrew clarke wrote:
Beware anyone building lang/ghc-8.8.3 from the ports tree. Building it
here on FreeBSD 12.1-REL AMD64 with Poudriere, the build ran out of swap,
despite the PC having 8 GB RAM, 8 GB swap and not much else running.
My /usr/local/etc/poudriere.conf:
BASEFS=/poudriere
ZPOOL=zroot
FREEBSD_HOST=http://mirror.internode.net/
POUDRIERE_DATA=/poudriere/data
RESOLV_CONF=/etc/resolv.conf
DISTFILES_CACHE=/usr/ports/distfiles
USE_TMPFS=yes
ALLOW_MAKE_JOBS=yes
KEEP_OLD_PACKAGES=yes
PARALLEL_JOBS=8
Maybe I can retune the last three parameters to use less memory. I've not
tried yet.
This isn't really a whinge, I'm just surprised it failed. I'd have thought
8 GB was enough.
(ghc is a build dependency of textproc/hs-pandoc)
Did you have something else building at the same time?
On my laptop with 16 Gb of RAM I also see OOM failures when building
multiple "heavy" packages (llvmXX, gccX, ghc, rust, libreoffice)
simultaneously. In this case I use -J poudriere option to limit number of
jobs.
Nothing else building.
This is a headless server, so I've no need to build something the size of
libreoffice or chromium. I've noticed llvm10 takes a long time to build, but
8 GB seems plenty of memory for it.
The -J option sounds like the way to go, provided I remember to use it
next time. Or I could instead set PARALLEL_JOBS=1 in poudriere.conf but then
build performance will suffer for every port, which isn't ideal.
But perhaps there's an option to limit make jobs just for a single port, set in
/usr/local/etc/poudriere.d/make.conf ? That would be nice.
You can do it for OPTIONS in make.conf (or poudriere make/set .conf's):
# Per port options
# category_portname_{UN}SET=[ OPTION ]
graphics_cairo_UNSET=OPENGL
graphics_cairo_SET=X11
This doesn't help for non-OPTIONS variables, but we have this recently
submitted feature/review:
https://reviews.freebsd.org/D24324
For use like:
devel_llvm80_VARS=DISABLE_MAKE_JOBS=yes
devel_llvm90_VARS=DISABLE_MAKE_JOBS=yes
This would satisfy this and other per-port specific build options cases.
___
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: Out of memory building lang/ghc-8.8.3
On 2020-05-05 14:19:50, Gleb Popov (arr...@freebsd.org) wrote: > On Tue, May 5, 2020 at 1:37 PM andrew clarke wrote: > > > Beware anyone building lang/ghc-8.8.3 from the ports tree. Building it > > here on FreeBSD 12.1-REL AMD64 with Poudriere, the build ran out of swap, > > despite the PC having 8 GB RAM, 8 GB swap and not much else running. > > > > My /usr/local/etc/poudriere.conf: > > > > BASEFS=/poudriere > > ZPOOL=zroot > > FREEBSD_HOST=http://mirror.internode.net/ > > POUDRIERE_DATA=/poudriere/data > > RESOLV_CONF=/etc/resolv.conf > > DISTFILES_CACHE=/usr/ports/distfiles > > USE_TMPFS=yes > > ALLOW_MAKE_JOBS=yes > > KEEP_OLD_PACKAGES=yes > > PARALLEL_JOBS=8 > > > > Maybe I can retune the last three parameters to use less memory. I've not > > tried yet. > > > > This isn't really a whinge, I'm just surprised it failed. I'd have thought > > 8 GB was enough. > > > > (ghc is a build dependency of textproc/hs-pandoc) > > > > Did you have something else building at the same time? > > On my laptop with 16 Gb of RAM I also see OOM failures when building > multiple "heavy" packages (llvmXX, gccX, ghc, rust, libreoffice) > simultaneously. In this case I use -J poudriere option to limit number of > jobs. Nothing else building. This is a headless server, so I've no need to build something the size of libreoffice or chromium. I've noticed llvm10 takes a long time to build, but 8 GB seems plenty of memory for it. The -J option sounds like the way to go, provided I remember to use it next time. Or I could instead set PARALLEL_JOBS=1 in poudriere.conf but then build performance will suffer for every port, which isn't ideal. But perhaps there's an option to limit make jobs just for a single port, set in /usr/local/etc/poudriere.d/make.conf ? That would be nice. ___ 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: Out of memory building lang/ghc-8.8.3
On Tue, May 5, 2020 at 1:37 PM andrew clarke wrote: > Beware anyone building lang/ghc-8.8.3 from the ports tree. Building it > here on FreeBSD 12.1-REL AMD64 with Poudriere, the build ran out of swap, > despite the PC having 8 GB RAM, 8 GB swap and not much else running. > > My /usr/local/etc/poudriere.conf: > > BASEFS=/poudriere > ZPOOL=zroot > FREEBSD_HOST=http://mirror.internode.net/ > POUDRIERE_DATA=/poudriere/data > RESOLV_CONF=/etc/resolv.conf > DISTFILES_CACHE=/usr/ports/distfiles > USE_TMPFS=yes > ALLOW_MAKE_JOBS=yes > KEEP_OLD_PACKAGES=yes > PARALLEL_JOBS=8 > > Maybe I can retune the last three parameters to use less memory. I've not > tried yet. > > This isn't really a whinge, I'm just surprised it failed. I'd have thought > 8 GB was enough. > > (ghc is a build dependency of textproc/hs-pandoc) > Did you have something else building at the same time? On my laptop with 16 Gb of RAM I also see OOM failures when building multiple "heavy" packages (llvmXX, gccX, ghc, rust, libreoffice) simultaneously. In this case I use -J poudriere option to limit number of jobs. > Cheers. > ___ > 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: New port: simh-hpdoc (PR 244395)
Hi! > I hate to bug people about this sort of thing, as I know there is > always a big queue. > > I submitted this PR a few weeks ago. It's simply a documentation > package so shouldn't take long. Done. > It's a dependency for two other ports that I am waiting to submit (see > the PR). I don't really want to submit them until this is safely > committed. Please always submit follow-up PRs and reference them in the first one. This allows for faster turn-around. -- p...@opsec.eu+49 171 3101372Now what ? ___ 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: Out of memory building lang/ghc-8.8.3
## andrew clarke (m...@ozzmosis.com): > Beware anyone building lang/ghc-8.8.3 from the ports tree. Building it > here on FreeBSD 12.1-REL AMD64 with Poudriere, the build ran out of swap, > despite the PC having 8 GB RAM, 8 GB swap and not much else running. I believe they sell phones with that amount of RAM these days, but they don't run ZFS on that phone as it's a "resource-constrained environment". ghc may eat quite some RAM (>2GB per process are not unheard of), you might have better luck if you don't use these: > USE_TMPFS=yes > ALLOW_MAKE_JOBS=yes > PARALLEL_JOBS=8 tmpfs uses your already scarce memory, and ALLOW_MAKE_JOBS will almost certainly run multiple ghc processes at the same time (it does so here). Regards, Christoph -- Spare Space ___ 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"
Out of memory building lang/ghc-8.8.3
Beware anyone building lang/ghc-8.8.3 from the ports tree. Building it here on FreeBSD 12.1-REL AMD64 with Poudriere, the build ran out of swap, despite the PC having 8 GB RAM, 8 GB swap and not much else running. My /usr/local/etc/poudriere.conf: BASEFS=/poudriere ZPOOL=zroot FREEBSD_HOST=http://mirror.internode.net/ POUDRIERE_DATA=/poudriere/data RESOLV_CONF=/etc/resolv.conf DISTFILES_CACHE=/usr/ports/distfiles USE_TMPFS=yes ALLOW_MAKE_JOBS=yes KEEP_OLD_PACKAGES=yes PARALLEL_JOBS=8 Maybe I can retune the last three parameters to use less memory. I've not tried yet. This isn't really a whinge, I'm just surprised it failed. I'd have thought 8 GB was enough. (ghc is a build dependency of textproc/hs-pandoc) Cheers. ___ 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"
New port: simh-hpdoc (PR 244395)
Hi! I hate to bug people about this sort of thing, as I know there is always a big queue. I submitted this PR a few weeks ago. It's simply a documentation package so shouldn't take long. It's a dependency for two other ports that I am waiting to submit (see the PR). I don't really want to submit them until this is safely committed. Can someone take a look, please? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244395 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: New port: mail/mmh feedback/commiter request
Hi! > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245346 > > It would be nice to get some feedback and maybe a commiter > for this port. Committed, thanks! -- p...@opsec.eu+49 171 3101372Now what ? ___ 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"
New port: mail/mmh feedback/commiter request
Hi https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245346 It would be nice to get some feedback and maybe a commiter for this port. Thanks satanist ___ 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"
ports: Need new future
Hi All! I think that for the ports menu options need a new "default" button (make rmconfig). -- - Alex. ___ 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"
