On 27 April 2012 00:45, Mike Miller <mtmil...@ieee.org> wrote:
> 2012/4/26 Carnë Draug <carandraug+...@gmail.com>:
>> On 26 April 2012 17:49, Mike Miller <mtmil...@ieee.org> wrote:
>>> 2012/4/26 Carnë Draug <carandraug+...@gmail.com>:
>>>> On 26 April 2012 13:00, Mike Miller <mtmil...@ieee.org> wrote:
>>>>> I've noticed a fair number of Makefiles that call mkoctfile instead of
>>>>> the $(MKOCTFILE) variable, this will not work as intended if compiling
>>>>> against an Octave in a non-standard path, right? Is this something
>>>>> that should be fixed per-package or across the board? For example,
>>>>> I'm working in comm, should I just submit a patch for comm's Makefile
>>>>> for now? Thanks.
>>>>
>>>> So all Makefile should use?
>>>>
>>>> ifndef MKOCTFILE
>>>> MKOCTFILE := mkoctfile -Wall
>>>> endif
>>>>
>>>> Is this correct? I'll guess that almost all packages will need this fix.
>>>
>>> Good point. True, I was a bit narrow in scope looking at comm because
>>> it has a configure script and already has a MKOCTFILE variable
>>> defined, oops :) I think I can patch that one as it is today, problem
>>> solved, patch forthcoming later.
>>>
>>> By the way, the current released communications-1.1.0 doesn't build
>>> against octave 3.6.1, is there a plan for a 1.1.1 release? I plan to
>>> contribute a few functions within the week.
>>
>> This package currently has no maintainer. Many other packages also
>> have no maintainer and I have been trying to make releases of them as
>> I find free time to do so. We are aware of this problem and it is
>> fixed on the development source (as you probably already noticed).
>
> I've been lurking on the list, I'm familiar with your efforts to clean
> up and keep the package releases going, great work, no complaints
> here! Yes, building from svn and running with that (addpath to point
> to the svn tree) works for me.
>
>> This package is a bit more complex and I'm not familiar with it all so
>> if you'd like to prepare a new release you are most welcome and it
>> would be very appreciated.
>
> Yes, any way I can help. Is there a script or procedure I can read up
> on how to make a release from the svn tree?
Ideally, the functions in the package have test blocks as well on
them. Check if they pass on the latest octave release. Update the NEWS
and DESCRIPTION file, svn export and tar.gz it. Get a list of all
changes since a specific date with ''svn log -v -r HEAD:{yyyy-mm-dd}".
The changes that will be user visible should be mentioned on NEWS
(things such as renaming the name of a class on source, such as LU to
galoisLU, do not need to be mentioned there).
There's a function on the admin section to make the packaging (see
admin/releasePKG.m). The comm package has a slightly more complex
Makefile than others (compare with general for example). If you can
make it simpler and easier to maintain in the future...
Carnë
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Octave-dev mailing list
Octave-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/octave-dev
