Date: Mon, 17 Aug 2015 17:57:46 +0300 From: Dmitry Marakasov <amdmi3@amdmi3.ru> To: marino@freebsd.org Cc: cyberbotx@cyberbotx.com, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r394456 - head/devel/doxygen Message-ID: <20150817145746.GW42382@hades.panopticon> In-Reply-To: <55D1DAD4.2090207@marino.st> References: <201508171226.t7HCQ8bY077008@repo.freebsd.org> <20150817123307.GA17641@hades.panopticon> <55D1DAD4.2090207@marino.st>
next in thread | previous in thread | raw e-mail | index | archive | help
* John Marino (freebsd.contact@marino.st) 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? Here we're talking not of systems which the port supports, but of systems which doxygen supports, as generated doxyfile is intended to be used in the outside world. The hardcoded path is 100% wrong regardless of a system, but I thought that instead of favoring BSD it may be better to stick to upstream/pola. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://amdmi3.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150817145746.GW42382>