[GenABEL-dev] LATEX error on autoreconf

Tue Oct 28 14:32:53 CET 2014

Hi Lennart,

Sorry If I am mistaken, but I was under the impression that installation and distribution was no longer under my control.

I am being asked for omicabelnomm from previous users and MPI support has been broken. 
Is there a way to set up a pipeline between you and Jürgen? Or an automated installable/updatable version for him to obtain from somewhere(svn/jenkins repo?)?

Best,

Alvaro
________________________________________
From: L.C. Karssen [lennart at karssen.org]
Sent: Tuesday, October 28, 2014 12:45 PM
To: Frank, Alvaro Jesus
Subject: Re: [GenABEL-dev] LATEX error on autoreconf

On 28-10-14 12:39, Frank, Alvaro Jesus wrote:
> Wait, this creates binaries?

no, it creates a tar.gz file with the source files. Automake looks for
the variables that end in _SOURCES, _DIST, _DATA and a few others to
determine what needs to be added to the tar.gz file.
That's why a 'make distcheck' run shouldn't fail. It may indicate you
didn't add all required files to Makefile.am (and thus not to the tar.gz
file).

Lennart.

> ________________________________________
> From: L.C. Karssen [lennart at karssen.org]
> Sent: Tuesday, October 28, 2014 12:36 PM
> To: Frank, Alvaro Jesus
> Subject: Re: [GenABEL-dev] LATEX error on autoreconf
>
> On 28-10-14 12:12, Frank, Alvaro Jesus wrote:
>> Sorry, but I do not know the process for the tar.
>
> set proper version number in the AC_INIT line of configure.ac, then run:
>
> ./configure
> make dist
>
>
> Lennart.
>
>>
>> -Alvaro
>> ________________________________________
>> From: L.C. Karssen [lennart at karssen.org]
>> Sent: Tuesday, October 28, 2014 9:07 AM
>> To: Frank, Alvaro Jesus
>> Subject: Re: [GenABEL-dev] LATEX error on autoreconf
>>
>> On 27-10-14 23:12, Frank, Alvaro Jesus wrote:
>>>
>>>     I just replied to it. Since we decided to keep things small and only for
>>>     Helmholtz, I think you sending him regular source.tar.gz files is the
>>>     best solution for now, while we prepare for a proper release of
>>>     OAnMM 1.0.
>>>
>>> Can we inform him of this?
>>
>> Sure! Go ahead.
>>
>>
>> Lennart.
>>
>>
>>>
>>> -Alvaro
>>> ________________________________________
>>> From: L.C. Karssen [lennart at karssen.org]
>>> Sent: Monday, October 27, 2014 2:55 PM
>>> To: Frank, Alvaro Jesus
>>> Subject: Re: [GenABEL-dev] LATEX error on autoreconf
>>>
>>> Hi Alvaro,
>>>
>>> On 27-10-14 14:41, Frank, Alvaro Jesus wrote:
>>>>
>>>> ________________________________________
>>>> From: L.C. Karssen [lennart at karssen.org]
>>>> Sent: Monday, October 27, 2014 2:22 PM
>>>> To: Frank, Alvaro Jesus
>>>> Subject: Re: [GenABEL-dev] LATEX error on autoreconf
>>>>
>>>> Hi Alvaro,
>>>>
>>>>
>>>> That would be the OmicABELnoMM section on www.genabel.org, which is not
>>>> created yet. Do you already have an account for that web site?
>>>>
>>>>
>>>> I have the one that lets me use svn and other related services.
>>>
>>> That's for R-forge.org. I'll send you login details for www.genabel.org
>>> as well.
>>>
>>>>
>>>> From this I understand that you consider OmicABELnoMM good enough for
>>>> world-wide production use?
>>>>
>>>>
>>>> I am not the one to make this call,
>>>
>>> I think this is a call made by you, me and Yurii. Given the current
>>> state of things, I would suggest to start on the OAnoMM page on
>>> www.genabel.org (maybe without making it publicly visible yet), while we
>>> work on ironing out the documentation and add the last few small
>>> features (e.g. possibility to compile without MPI).
>>>
>>>
>>>> but Helmholtz is using it and
>>>> helping me to fix problems, add features and run test analisys to
>>>> corroborate its working condition. They and I need to have a working
>>>> installable version, which I had Friday but not anymore. With regards to
>>>> them it can be considered an excetion and not "world-wide production
>>>> use" do to mutual work benefits.
>>>
>>> Great! Let's consider the current status 'v1.0 beta' then. Only
>>> 'officially' available to Helmholtz. I say 'officially' because
>>> obviously every one could do an SVN checkout.
>>>
>>>>
>>>> If so, we should start working on the section
>>>> of www.genabel.org.
>>>> If you're not ready for worldwide deployment, you can send the (beta)
>>>> users the tar.gz file generated by running 'make dist'.
>>>>
>>>> This could help Jürgen. See his email.
>>>
>>> I just replied to it. Since we decided to keep things small and only for
>>> Helmholtz, I think you sending him regular source.tar.gz files is the
>>> best solution for now, while we prepare for a proper release of OAnMM 1.0.
>>>
>>>>
>>>> I wouldn't give an e-mail. We have forum.genabel.org for that. For now
>>>> questions should be asked in the general "GenABEL" section. If the
>>>> number of questions becomes large we can consider to split them off in a
>>>> separate forum, like we did for ProbABEL.
>>>>
>>>>
>>>> My bad, I already gave out our devlist email (it is open and recommended
>>>> on the site to use it anyway). It has been Helmholtz only anyway.
>>>
>>> No problem. Given that we're still in the pre-release phase I'd say it
>>> is fine on the dev list.
>>>
>>>>
>>>> I do feel important that someone gets in contact with Christian
>>>> regarding the status of OmicABELnoMM, It seems to me that noone besides
>>>> me and a few of Christians workers know the status of OmicABELnoMM. It
>>>> is hard for me to get a hold of him and it is imperative that all
>>>> parties involved are up to date with the status.
>>>
>>> Good point. I have heard that Yurii, Yakov and Sodbo will come to
>>> München in the week of November 10. Paolo will be there on Thursday
>>> evening and Friday IIRC. Unfortunately I have to teach on Thu and Fri,
>>> but I can come on Monday early and leave on Tuesday evening. Will you be
>>> there in that week as well? That would be a good time to discuss the
>>> 'management' side of things:
>>> - what to do before v1.0 (my suggestions: documentation and no-MPI
>>> option, possible also openMPI and MPICH2 compatibility if not too much
>>> work for you)
>>> - publication strategy (1 paper or 2?)
>>> - maintenance strategy (who will do support and maintenance and for how
>>> long)
>>>
>>>
>>> Best,
>>>
>>> Lennart.
>>>
>>>>
>>>> best,
>>>>
>>>> Alvaro
>>>>
>>>
>>> --
>>> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
>>> L.C. Karssen
>>> Utrecht
>>> The Netherlands
>>>
>>> lennart at karssen.org
>>> http://blog.karssen.org
>>> GPG key ID: A88F554A
>>> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
>>>
>>
>> --
>> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
>> L.C. Karssen
>> Utrecht
>> The Netherlands
>>
>> lennart at karssen.org
>> http://blog.karssen.org
>> GPG key ID: A88F554A
>> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
>>
>
> --
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> L.C. Karssen
> Utrecht
> The Netherlands
>
> lennart at karssen.org
> http://blog.karssen.org
> GPG key ID: A88F554A
> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
>

--
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
L.C. Karssen
Utrecht
The Netherlands

lennart at karssen.org
http://blog.karssen.org
GPG key ID: A88F554A
-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-