Date: Mon, 17 Aug 2015 14:07:08 +0100 From: David Chisnall <theraven@FreeBSD.org> To: Mathieu Arnold <mat@FreeBSD.org> Cc: marino@freebsd.org, Dmitry Marakasov <amdmi3@amdmi3.ru>, 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: <DA1E6B3A-5191-4E04-8629-64C7C3CAFF60@FreeBSD.org> In-Reply-To: <9EAD92E185BB26C89D93D145@atuin.in.mat.cc> References: <201508171226.t7HCQ8bY077008@repo.freebsd.org> <20150817123307.GA17641@hades.panopticon> <55D1DAD4.2090207@marino.st> <9EAD92E185BB26C89D93D145@atuin.in.mat.cc>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17 Aug 2015, at 13:05, Mathieu Arnold <mat@FreeBSD.org> wrote: >=20 > +--On 17 ao=C3=BBt 2015 15:00:04 +0200 John Marino = <freebsd.contact@marino.st> > wrote: > | 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. > |=20 > | For FreeBSD and DragonFly, /usr/bin/perl is wrong. Why wouldn't = ports > | tailor doxygen files for those two systems? > |=20 > | 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? > |=20 > | Maybe I'm missing something? >=20 > I guess it's about people using doxygen on FreeBSD to generate stuff = that > they'll use outside of FreeBSD will get a bad shebang in the stuff = that was > generated. What=E2=80=99s wrong with #!/usr/bin/env perl ? David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DA1E6B3A-5191-4E04-8629-64C7C3CAFF60>