Re: Re: Octave in Google Summer of Code 2013 / Low Level I/O

[Juan Pablo Carbajal]

On Thu, Feb 28, 2013 at 2:32 PM, Stefan Mahr <address@hidden> wrote:
>
>
> Gesendet: Donnerstag, 28. Februar 2013 um 14:15 Uhr
> Von: "Juan Pablo Carbajal" <address@hidden>
> An: "Carnë Draug" <address@hidden>
> Cc: "Stefan Mahr" <address@hidden>, "Andrius Sutas"
> <address@hidden>, address@hidden
> Betreff: Re: Octave in Google Summer of Code 2013 / Low Level I/O
> On Thu, Feb 28, 2013 at 1:44 PM, Juan Pablo Carbajal
> <address@hidden> wrote:
>> On Thu, Feb 28, 2013 at 1:38 PM, Carnë Draug <address@hidden>
>> wrote:
>>> On 28 February 2013 12:18, Juan Pablo Carbajal <address@hidden>
>>> wrote:
>>>> On Tue, Feb 26, 2013 at 10:49 PM, Stefan Mahr <address@hidden> wrote:
>>>>> Juan Pablo Carbajal wrote:
>>>>>> @Stefan: Please merge your code into the package and add yourself as a
>>>>>> maintainer. Let me know when you have committed your changes so we can
>>>>>> prepare a new release.
>>>>>>
>>>>>> We are on the move!
>>>>>
>>>>> Hi JPi, hi Andrius,
>>>>>
>>>>> merging is done. Compiling on linux and cygwin works. I did not test
>>>>> *bsd.
>>>>>
>>>>> With mingw (mxe-octave) only tcp works, all other interfaces fail to
>>>>> compile. Should be acceptable for now.
>>>>>
>>>>>
>>>>> Stefan
>>>>
>>>> Hi,
>>>>
>>>> I noticed that the package needs to be boostraped before it can be
>>>> distributed. This breaks the current version of releasePKG.
>>>> @Carnë: What would be the procedure with packages like this?
>>>
>>> The procedure to release package like this is that the package manager
>>> runs ./bootstrap first, and then create a tarball of the result. Also,
>>> remove the "autom4te.cache" directory that may have been generated.
>>> Whether to also remove the bootstrap and configure.ac/in files from
>>> the tarball, is up to the package manager (probably we should settle
>>> on something?).
>>>
>>> Carnë
>>
>> ok, I am modifying releasePKG to run bootstrap and remove the
>> "autom4te.cache" directory. The other files may help to debug user
>> problems
>
> I am getting
> warning: marking 'gpib' as not implemented
> warning: marking 'gpib_read' as not implemented
> warning: marking 'gpib_write' as not implemented
> warning: marking 'gpib_timeout' as not implemented
> warning: marking 'gpib_close' as not implemented
>
> Is gpib properly documented?
>
> I assume gpib cannot be build since linux-gpib is not installed. An option
> would be to make a dummy function if libs are not installed.
>

The best would be to print a message telling the user they need that.
I am not talking about a big chekcing, just a message. Cause in the
case users use the system package manger it should it by itself

Also, we will get some complaints from the Debian package managers, probably.