Re: su2 for debian
On Friday 15 January 2016 18:22:12 Ghislain Vaillant wrote:
> Hey Mauro,
>
> > After compilation it gives me a few lintian errors:
> >
> > Now running lintian...
> > E: su2: subdir-in-usr-bin usr/bin/SU2/
> > E: su2: subdir-in-usr-bin usr/bin/SU2/eval/
> Self-explanatory, no sub-directories under usr/bin. Only entry points or
> pure scripts.
Should I investigate override_dh_install ?
> > E: su2: info-document-missing-dir-section usr/share/info/automake-
> > history.info.gz
> > E: su2: info-document-missing-dir-entry usr/share/info/automake-
> > history.info.gz
>
> Not sure why you need to install this?
I did nothing. Standard debhelper command "dh $@" is doing that.
> > W: su2: binary-without-manpage usr/bin/patient_designspace.py
> > W: su2: binary-without-manpage usr/bin/set_ffd_design_var.py
> > W: su2: binary-without-manpage usr/bin/shape_optimization.py
>
> Self-explanatory. Installed scripts *should* have an accompanying
> manpage. This is often overridden in case the scripts have nice help
> messages callable via -h or --help.
So what should the workaround be ? Should I create those missing manpages if
there is no nice help ?
> > W: su2: executable-not-elf-or-script usr/bin/SU2/opt/__init__.py
> > W: su2: executable-not-elf-or-script usr/bin/SU2/eval/__init__.py
>
> Probably due to the fact that the whole SU2 package is installed under
> usr/bin instead of the system site-packages. As far as I see it, the
> content of usr/bin/SU2 should be in usr/lib/python3/dist-packages and
> the entry-points under usr/bin.
>
What do you mean by "dist-packages" ?
I agree that most lintian reports are self-explanatory but since I have no
experience with debhelper often I cannot sort out how to eliminate those
warnings and errors.
One more question: this program seems to have a configure bug, since the
command:
override_dh_auto_configure:
dh_auto_configure -- --disable-metis --disable-tecio
disables the last one, tecio, only. What to do in such a case ?
thanks,
Mauro
--
Reply to: