[MacPorts] #27993: new port liblouisxml: Braille transcription services for xml documents

[MacPorts]

#27993: new port liblouisxml: Braille transcription services for xml documents
----------------------------------------+-----------------------------------
 Reporter:  boris.dusek@…               |       Owner:  ryandesign@…           
     Type:  submission                  |      Status:  assigned               
 Priority:  Normal                      |   Milestone:                         
Component:  ports                       |     Version:  1.9.2                  
 Keywords:  braille a11y accessibility  |        Port:  liblouisxml            
----------------------------------------+-----------------------------------
Changes (by ryandesign@…):

  * status:  new => assigned
  * owner:  macports-tickets@… => ryandesign@…


Old description:

> Please comment and/or commit.
>
> I also explicitely ask for review of two things:
>
> 1. the line "depends_build port:pkgconfig".  The library searches for
> libxml2 and liblouis using pkgconfig.  I don't know which port then
> should depend on pkgconfig - whether the ones that are declaring their
> existence using pkgconfig (like libxml2 and liblouis), or the ones that
> use pkgconfig to find other libraries (liblouisxml).
>
> 2. I also encountered problem with filesystem:
>
> Warning: violation by /opt/local/info
> Warning: violation by /opt/local/man
> Warning: liblouisxml violates the layout of the ports-filesystems!
>
> I solved this (after consulting Raim in IRC) by adding the line
> "configure.args      --mandir=${prefix}/share/man
> --infodir=${prefix}/share/info".  But I wonder why MacPorts does not pass
> these arguments itself since it supports autoconf-based systems out-of-
> the-box and should know these dark corners (so that portwriters don't
> have to take care of them in every port).
>
> Thanks.

New description:

 Please comment and/or commit.

 I also explicitely ask for review of two things:

 1. the line "depends_build port:pkgconfig".  The library searches for
 libxml2 and liblouis using pkgconfig.  I don't know which port then should
 depend on pkgconfig - whether the ones that are declaring their existence
 using pkgconfig (like libxml2 and liblouis), or the ones that use
 pkgconfig to find other libraries (liblouisxml).

 2. I also encountered problem with filesystem:

 {{{
 Warning: violation by /opt/local/info
 Warning: violation by /opt/local/man
 Warning: liblouisxml violates the layout of the ports-filesystems!
 }}}

 I solved this (after consulting Raim in IRC) by adding the line
 "configure.args      --mandir=${prefix}/share/man
 --infodir=${prefix}/share/info".  But I wonder why MacPorts does not pass
 these arguments itself since it supports autoconf-based systems out-of-
 the-box and should know these dark corners (so that portwriters don't have
 to take care of them in every port).

 Thanks.

--

Comment:

 Thanks for the port!

 Replying to [ticket:27993 boris.dusek@…]:
 > 1. the line "depends_build port:pkgconfig".  The library searches for
 libxml2 and liblouis using pkgconfig.  I don't know which port then should
 depend on pkgconfig - whether the ones that are declaring their existence
 using pkgconfig (like libxml2 and liblouis), or the ones that use
 pkgconfig to find other libraries (liblouisxml).

 Since it is liblouisxml that uses pkg-config at build time, it is
 liblouisxml that needs the build dependency on port:pkgconfig.

 > 2. I also encountered problem with filesystem:  [[br]]
 >  [[br]]
 > Warning: violation by /opt/local/info [[br]]
 > Warning: violation by /opt/local/man [[br]]
 > Warning: liblouisxml violates the layout of the ports-filesystems!
 [[br]]
 >  [[br]]
 > I solved this (after consulting Raim in IRC) by adding the line
 "configure.args      --mandir=${prefix}/share/man
 --infodir=${prefix}/share/info".  But I wonder why MacPorts does not pass
 these arguments itself since it supports autoconf-based systems out-of-
 the-box and should know these dark corners (so that portwriters don't have
 to take care of them in every port).

 Most autoconfed software knows (because it obeys the FHS) that this is
 where those files should go and so those arguments would be superfluous.
 Most non-autoconfed software knows this as well. In other words, it is an
 exceptional case to need to specify this at all. Some software that
 doesn't already know this does not respond to the --mandir or --infodir
 configure arguments either; some might silently ignore it, some might
 complain. It is therefore better for the ports that require special
 handling for the mandir and infodir to do so themselves, in whatever way
 is appropriate for that software.

-- 
Ticket URL: <https://trac.macports.org/ticket/27993#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS