Date: Sun, 22 Jul 2018 08:28:41 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 229773] sysutils/dupd: update to version 1.7 Message-ID: <bug-229773-7788-l2UqEm7TZF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-229773-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-229773-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229773 --- Comment #7 from jyri@virkki.com --- Will the port build pass in any prefix other than /usr/local in practice? I can make it take a var (e.g. LIB_PREFIX) and if it set use it as-is, or if not set, default it to /usr/local OTOH, while I'm all for making it flexible I also don't want to add clutter that nobody will use. So if the port build system will ultimately just alwa= ys pass in /usr/local as the prefix, might as well leave it as is. But if this= can vary in FreeBSD installations, then it's worth making it configurable. I haven't done any meaningful testing between -O2 vs. -O3 so can't really s= ay. Perhaps -O2 is fine. I also have not done any performance testing on FreeBS= D. But if you run into any performance weirdness on FreeBSD please file a bug, I'll check it out. I primarily test on Linux (w/gcc) and secondarily on Sol= aris (w/Sun cc). dupd attitude is that RAM is there to be used, so it doesn't limit memory u= sage unless you ask (--buflimit). If you want, send me output of 'dupd scan -v' = and I'll play around with a similar file set in case there is any unwarranted inefficiency there. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-229773-7788-l2UqEm7TZF>