Bug#409849: First rough draft of an afni Debian package
On Mon, Oct 19, 2009 at 03:53:29PM -0400, Judd Storrs wrote:
> Excellent work! I have two updates.
>
> The first adds an afni-dev package to include headers needed to use libmri
> etc as well as to compile AFNI plugins. I wasn't sure where these should
> go--this places them inside /usr/include/afni.
The place is fine, but how did you determine the subset of headers that
should go into it. If we can automize that, it might scale a bit better
with the future AFNI development.
However, the more serious problem is that having a -dev package also
implies that the libs can be used elsewhere -- which is actually not
the case. Without a proper versioning scheme and sane interface policies
we cannot expose the shared libs (that I imagined to be internal
convenience libs) like this. What could be done is adding static libs to
the -dev package. However, already now it is significant pain to build
shared libs alone -- building both is even more tricky using AFNI's
cumbersome build system...
I got a patch from Bernd Feige that replaces the Makefiles with a cmake
setup -- which is wonderful and will solve all of our problems at once.
However, it is pretty invasive and such is usually discouraged for
Debian packaging. Right now I am reluctant to use that for the package,
but if we want a fully functional package with no compromise, there
might be no way around it. Sadly, Bernd submitted his patch upstream
some time ago and it was not accepted ....
> The second patch allows either openmotif or lesstif to be used.
I'm pretty much in favor of this change, however, it might be that we
have to revert that at some point, since openmotif is non-free and
package in main must not depend on anything else but packages in main.
Although in this case it is an optional alternative build-dependency --
so it might work -- we'll see...
> Again, wonderful work!
Thanks, but I think more should be done to the default configuration.
AFNI.afnirc and AFNI.sumarc are now simply shipped as examples in the
afni-common package, but I guess they should become somewhat more
functional. My own config scheme in /etc/afni/afni.sh takes care of the
most critical settings, but the majority is left untouched. I am not
sure about implementing a proper default system-wide config setup --
right now this per-user thingie that comes with AFNI feels incomplete
and suboptimal. Advice is most welcome, since I am not really a
proficient AFNI user.
Thanks,
Michael
--
GPG key: 1024D/3144BE0F Michael Hanke
http://mih.voxindeserto.de
Reply to: