[Neurodebian-users] AFNI not available?

[Bennet Fauber]

I saw that someone else inquired about AFNI and Ubuntu 16.04, but I'll
reply here.

I don't know its scope -- local, regional, national -- but I believe
there is another 'BrainHack' planned here at Michigan for October.  If
that is more than just local, would getting some of the work done on
the NeuroDebian packages -- AFNI, et al. -- to resolve issues,
especially by and for the Ubuntu users -- be a suitable topic for
that?

>From the References section of http://neuro.debian.net/proj_afni.html
I looked at the three links.

The last activity on Debian, "ITP bug report with information on the
packaging progress." appars to be from Nov 2010.

The last activity at "Git repository with the full source code and the
Debian packaging." appears to be a branch switch by Yaroslav back to
the build branch, prior to which last activity seems to be a year ago.

>From the pages at "List of patches applied to the Debian package (i.e.
the difference to the upstream AFNI source code)." that appears to
have stopped updating about a year ago.

I'm not criticizing, but it seems that quite a bit of time has
elapsed, so I'm wondering if there is anything more up-to-date on the
status porting upstream and/or what would need to be done to make it
so?

I have a busy month or two ahead of me, and I'm only the system
administrator here, but if there are people who are interested in
trying to get this going, I would be willing to help as best I can
starting probably in August.

-- bennet




On Thu, May 26, 2016 at 9:28 AM, Alex Waite <alexqw85 at gmail.com> wrote:
> On 05/26/2016 02:18 PM, Bennet Fauber wrote:
>>
>> Are there techical issues that keep it from running properly, or is it
>> the licensing issues I see in the github:ND/afni repository?
>
>
> The licensing is mostly a non-issue. The major problems have been resolved
> (AFAIK).
>
> The thing that's holding us back is that building AFNI is a PITA because we
> have our own CMake build system, and thus have to port changes over with
> (nearly) every release.
>
> And, for added fun, recent libnifti (IIRC) changes have led to some fun
> versioning issues. I don't know how all that turned out, but Yarik may have
> more info on that.
>
>> How old a Debian would we have to pull to get an AFNI that works?  (I
>> can check the VM image, if it works there?)
>
>
> No idea. Yarik would know better.
>
>> If there are issues that I can address and contribute to pushing this
>> forward, let me know.  I can scrounge some time for this (but no
>> promises as to quantity).
>
>
> Help is /always/ welcome. I've been 1-2 weeks away from having the time to
> focus on it for... about 1 year now. ;-)
>
> The real fix, which upstream seems to be open to, is rounding out our CMake
> patches to support other target distros and then upstreaming it. That would
> take away the majority of the headaches, and AFNI could then be updated
> fairly regularly. Everybody wins.
>
> ---Alex
>
>
>
>
>
> _______________________________________________
> Neurodebian-users mailing list
> Neurodebian-users at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/neurodebian-users