svn commit: r394456 - head/devel/doxygen

[Mathieu Arnold]

+--On 17 août 2015 14:07:08 +0100 David Chisnall <theraven at FreeBSD.org>
wrote:
| On 17 Aug 2015, at 13:05, Mathieu Arnold <mat at FreeBSD.org> wrote:
|> 
|> +--On 17 août 2015 15:00:04 +0200 John Marino
|> <freebsd.contact at 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.
|> | 
|> | 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?
|> 
|> 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’s wrong with #!/usr/bin/env perl ?

Nothing, it's what I said in my other email :-)

-- 
Mathieu Arnold
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 949 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/svn-ports-head/attachments/20150817/ad410f6e/attachment.bin>