Date: Mon, 17 Aug 2015 15:00:04 +0200 From: John Marino <freebsd.contact@marino.st> To: Dmitry Marakasov <amdmi3@amdmi3.ru>, cyberbotx@cyberbotx.com Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r394456 - head/devel/doxygen Message-ID: <55D1DAD4.2090207@marino.st> In-Reply-To: <20150817123307.GA17641@hades.panopticon> References: <201508171226.t7HCQ8bY077008@repo.freebsd.org> <20150817123307.GA17641@hades.panopticon>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/17/2015 2:33 PM, Dmitry Marakasov wrote: > The problem: doxygen generated Doxyfiles list perl path in them as > /usr/bin/perl, while on FreeBSD perl resides in /usr/local/bin/perl. > However, doxyfiles are used on other systems as well, and /usr/bin/perl > seems to me more widely used path. Imo this should not ever be > hardcoded. For FreeBSD and DragonFly, /usr/bin/perl is wrong. Why wouldn't ports tailor doxygen files for those two systems? Or to put it another way: Why would you advocating something this is 100% wrong on the systems that ports support in favor of "other systems" that aren't supported? Maybe I'm missing something? John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55D1DAD4.2090207>