Re: [OctDev] Comm package
On 11 May 2012, at 23:18, Mike Miller wrote: > Hey Jordi, thanks for getting this moving. I'm no expert on releases, > but this isn't working: > * filename must match package name, so rename to communications-1.1.1.tar.gz > Non-fatal: > * would be nice if directory in the tar were the same name instead of "lol" > :) > * good that you autogen'd the configure script in there, but would > be nice to delete autom4te.cache > * might as well delete .svnignore files too * also, please remember to generate the html docs with the "generate_package_html" function from the "generate_html" package and post them as well. > Do the devs have a preference if the directory name in the tar is > $package or $package-$version? > > -- > mike c. -- 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
Re: [OctDev] errors in econometrics package
On 11 May 2012 16:28, Michael Creel wrote:
> On Fri, May 11, 2012 at 1:47 PM, Carnë Draug wrote:
>> On 11 May 2012 12:32, Levente Torok wrote:
>>> On Fri, May 11, 2012 at 1:22 PM, Carnë Draug
>>> wrote:
On 11 May 2012 07:59, Levente Torok wrote:
> I wanted to analyze gmm_exampe.m from econometrics package recently
> installed but I found that it called a lot of deprecated functions.
> I tracked them and replaced. Now it seems to be working.
> I wish I could submit these modifications back to the package sources
> but as I see I cannot find the way to patch it in the svn tree where I
> found several versions of the corresponding file so I'd rather not to
> touch it
> instead I thought I share these modifications. I hope someone can put
> it the package
>
> gmm_example.m:
> replace call of poisson_rnd with poissrnd
> str2mat call str2mat with char
>
> poisson_moments.m :
> replace call of dmult.m with diag(A)*B
>
> scale_data.m:
> replace call of dmult.m with diag(A)*B
>
> gmm_results.m
> replace call of str2mat with char
> chisquare_cdf with chi2cdf
> normal_cdf with normcdf
>
> poisson_moments.m:
> replace call of dmult.m with diag(A)*B
>
> unscale_parameters.m
> replace call of nth with {1}{2}
this is the wrong mailing list. Octave packages belong to octave-forge
so bugs should be reported there.
All the problems you mentioned have already been fixed on the
development version (that's why you couldn't patch against the SVN
tree) we just need someone to make a new release of the package.
>>>
>>> I see. Thanks. It was kind of a problematic stuff to me.
>>> Wouldn't it be possible to keep forge and octave in sync?
>>> I mean I would let someone install forge package unless it is
>>> absolutely sure that it will function with the installed octave
>>> version.
>>
>> Yes, it's possible and there's more who would like that to happen.
>> Unfortunately, there's no one around with the means to put something
>> like that in place.
>>
> About OF package releases, I haven't kept up
> with how that works.
It's quite simple and explained in http://octave.sourceforge.net/developers.html
Basically, cd into main/econometrics and run
svn log -v -r HEAD:{-mm-dd}
with the date from last release. This will generate a list of commits
since the last release. Write them in a NEWS file. Update the version
number and date on DESCRIPTION. Then
svn export ../econometrics ~/econometrics
cd ~
make sure to remove all .svnignore and othr things not necessary in
econometrics/
tar czf econometrics-x.y.z.tar.gz econometrics/
install the package you just generated and generate the documentation
pkg install -forge generate_html;
pkg load generate_html;
generate_package_html ('econometrics', 'econometrics-html', 'octave-forge');
Then exit octave prompt and
tar czf econometrics-html.tar.gz econometrics-html/
That's it. Upload both files to the forum and I'll upload them to the server.
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
Re: [OctDev] Comm package
On Sat, May 12, 2012 at 3:34 AM, c. wrote: > > On 11 May 2012, at 23:18, Mike Miller wrote: > >> Hey Jordi, thanks for getting this moving. I'm no expert on releases, >> but this isn't working: >> * filename must match package name, so rename to communications-1.1.1.tar.gz >> Non-fatal: >> * would be nice if directory in the tar were the same name instead of "lol" >> :) >> * good that you autogen'd the configure script in there, but would >> be nice to delete autom4te.cache >> * might as well delete .svnignore files too > * also, please remember to generate the html docs with the > "generate_package_html" function from the "generate_html" package > and post them as well. Yes, did all that including the html docs and that is up on the package release forum now. -- mike -- 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
Re: [OctDev] Comm package
On 12 May 2012 13:40, Mike Miller wrote: > On Sat, May 12, 2012 at 3:34 AM, c. wrote: >> >> On 11 May 2012, at 23:18, Mike Miller wrote: >> >>> Hey Jordi, thanks for getting this moving. I'm no expert on releases, >>> but this isn't working: >>> * filename must match package name, so rename to >>> communications-1.1.1.tar.gz >>> Non-fatal: >>> * would be nice if directory in the tar were the same name instead of >>> "lol" :) >>> * good that you autogen'd the configure script in there, but would >>> be nice to delete autom4te.cache >>> * might as well delete .svnignore files too >> * also, please remember to generate the html docs with the >> "generate_package_html" function from the "generate_html" package >> and post them as well. > > Yes, did all that including the html docs and that is up on the > package release forum now. Yes, I see it now. You forgot to update the date of release. It's ok, I fixed that on my side. What I noticed is that communications now no longer has marcumq because it moved into signal. I should make a new release of signal so that there's no period without that function available. 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
Re: [OctDev] Comm package
On Sat, May 12, 2012 at 8:50 AM, Carnë Draug wrote: > On 12 May 2012 13:40, Mike Miller wrote: >> On Sat, May 12, 2012 at 3:34 AM, c. wrote: >>> >>> On 11 May 2012, at 23:18, Mike Miller wrote: >>> Hey Jordi, thanks for getting this moving. I'm no expert on releases, but this isn't working: * filename must match package name, so rename to communications-1.1.1.tar.gz Non-fatal: * would be nice if directory in the tar were the same name instead of "lol" :) * good that you autogen'd the configure script in there, but would be nice to delete autom4te.cache * might as well delete .svnignore files too >>> * also, please remember to generate the html docs with the >>> "generate_package_html" function from the "generate_html" package >>> and post them as well. >> >> Yes, did all that including the html docs and that is up on the >> package release forum now. > > Yes, I see it now. You forgot to update the date of release. It's ok, > I fixed that on my side. What I noticed is that communications now no > longer has marcumq because it moved into signal. I should make a new > release of signal so that there's no period without that function > available. Thanks, I realized that too about the function moving, might as well put out what we have now. I just added a NEWS item for what I've changed in signal. -- mike -- 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
Re: [OctDev] Comm package
On 12 May 2012 14:04, Mike Miller wrote: > On Sat, May 12, 2012 at 8:50 AM, Carnë Draug wrote: >> On 12 May 2012 13:40, Mike Miller wrote: >>> On Sat, May 12, 2012 at 3:34 AM, c. wrote: On 11 May 2012, at 23:18, Mike Miller wrote: > Hey Jordi, thanks for getting this moving. I'm no expert on releases, > but this isn't working: > * filename must match package name, so rename to > communications-1.1.1.tar.gz > Non-fatal: > * would be nice if directory in the tar were the same name instead of > "lol" :) > * good that you autogen'd the configure script in there, but would > be nice to delete autom4te.cache > * might as well delete .svnignore files too * also, please remember to generate the html docs with the "generate_package_html" function from the "generate_html" package and post them as well. >>> >>> Yes, did all that including the html docs and that is up on the >>> package release forum now. >> >> Yes, I see it now. You forgot to update the date of release. It's ok, >> I fixed that on my side. What I noticed is that communications now no >> longer has marcumq because it moved into signal. I should make a new >> release of signal so that there's no period without that function >> available. > > Thanks, I realized that too about the function moving, might as well > put out what we have now. I just added a NEWS item for what I've > changed in signal. I found a problem with signal because of the circular dependency with communications. While they can be installed at the same time, as soon as one tries to load them it fails with a max_recursion_depth exceeded error. This can be work around with pkg load -nodeps but that should not be an option for a release. Any thoughts? 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
Re: [OctDev] Comm package
On Sat, May 12, 2012 at 9:48 AM, Carnë Draug wrote: > On 12 May 2012 14:04, Mike Miller wrote: >> On Sat, May 12, 2012 at 8:50 AM, Carnë Draug >> wrote: >>> On 12 May 2012 13:40, Mike Miller wrote: On Sat, May 12, 2012 at 3:34 AM, c. wrote: > > On 11 May 2012, at 23:18, Mike Miller wrote: > >> Hey Jordi, thanks for getting this moving. I'm no expert on releases, >> but this isn't working: >> * filename must match package name, so rename to >> communications-1.1.1.tar.gz >> Non-fatal: >> * would be nice if directory in the tar were the same name instead of >> "lol" :) >> * good that you autogen'd the configure script in there, but would >> be nice to delete autom4te.cache >> * might as well delete .svnignore files too > * also, please remember to generate the html docs with the > "generate_package_html" function from the "generate_html" package > and post them as well. Yes, did all that including the html docs and that is up on the package release forum now. >>> >>> Yes, I see it now. You forgot to update the date of release. It's ok, >>> I fixed that on my side. What I noticed is that communications now no >>> longer has marcumq because it moved into signal. I should make a new >>> release of signal so that there's no period without that function >>> available. >> >> Thanks, I realized that too about the function moving, might as well >> put out what we have now. I just added a NEWS item for what I've >> changed in signal. > > I found a problem with signal because of the circular dependency with > communications. While they can be installed at the same time, as soon > as one tries to load them it fails with a max_recursion_depth exceeded > error. This can be work around with pkg load -nodeps but that should > not be an option for a release. Any thoughts? I let you add it at the time but I thought it might be a problem :) Honestly I think bitrevorder should be rewritten to not use the communications functions. You could put it out as it was, without the dependency, and we'd be no worse than before, and in the future I'd like to fix it to get rid of the bi2de/de2bi calls. -- mike -- 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
Re: [OctDev] Comm package
On 12 May 2012 14:53, Mike Miller wrote: > On Sat, May 12, 2012 at 9:48 AM, Carnë Draug wrote: >> On 12 May 2012 14:04, Mike Miller wrote: >>> On Sat, May 12, 2012 at 8:50 AM, Carnë Draug >>> wrote: On 12 May 2012 13:40, Mike Miller wrote: > On Sat, May 12, 2012 at 3:34 AM, c. wrote: >> >> On 11 May 2012, at 23:18, Mike Miller wrote: >> >>> Hey Jordi, thanks for getting this moving. I'm no expert on releases, >>> but this isn't working: >>> * filename must match package name, so rename to >>> communications-1.1.1.tar.gz >>> Non-fatal: >>> * would be nice if directory in the tar were the same name instead of >>> "lol" :) >>> * good that you autogen'd the configure script in there, but would >>> be nice to delete autom4te.cache >>> * might as well delete .svnignore files too >> * also, please remember to generate the html docs with the >> "generate_package_html" function from the "generate_html" package >> and post them as well. > > Yes, did all that including the html docs and that is up on the > package release forum now. Yes, I see it now. You forgot to update the date of release. It's ok, I fixed that on my side. What I noticed is that communications now no longer has marcumq because it moved into signal. I should make a new release of signal so that there's no period without that function available. >>> >>> Thanks, I realized that too about the function moving, might as well >>> put out what we have now. I just added a NEWS item for what I've >>> changed in signal. >> >> I found a problem with signal because of the circular dependency with >> communications. While they can be installed at the same time, as soon >> as one tries to load them it fails with a max_recursion_depth exceeded >> error. This can be work around with pkg load -nodeps but that should >> not be an option for a release. Any thoughts? > > I let you add it at the time but I thought it might be a problem :) > Honestly I think bitrevorder should be rewritten to not use the > communications functions. You could put it out as it was, without the > dependency, and we'd be no worse than before, and in the future I'd > like to fix it to get rid of the bi2de/de2bi calls. You're right, I didn't foresaw any other problems aside the install. About fixing this, it just occured to me that I can always make those 2 functions subfunctinos to bitrevorder. It's not the cleanest option but seems better than not listing the dependency. What do you think? 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
Re: [OctDev] Installing communications pkg in octave 3.4.x: -lhdf5 missing in mkoctfile
Hi Marco and Mike, Thanks, I will try the new release of the pkg, Amal Ekbal > discussed some time ago. > > http://thread.gmane.org/gmane.comp.gnu.octave.devel/6616/focus=6675 > > next release will include it > > Marco On May 11, 2012, at 9:21 PM, Mike Miller wrote: > On Fri, May 11, 2012 at 8:50 PM, Amal Ekbal wrote: >> I tried that and indeed I get the answers you expected. >> >> $ mkoctfile -p OCTINCLUDEDIR >> /opt/local/include/octave-3.4.3/octave >> $ grep HDF5_LIBS /opt/local/include/octave-3.4.3/octave/oct-conf.h >> #ifndef OCTAVE_CONF_HDF5_LIBS >> #define OCTAVE_CONF_HDF5_LIBS "-lhdf5" >> >> I am not sure how to interpret this:- Does this mean that the "-lhdf5" >> should have been included without having to edit the mkoctfile explicitly? >> Then, I am not sure why this directive was ignored during pkg install. > > Yes, exactly, these are the commands the Makefile uses to get the > flags to pass to mkoctfile when it builds the package. You shouldn't > have to modify anything. I'm not sure what to make of it that it's > not working in this case. > > A new release of the communications package should be available for > download soon, you can try that and see if it works better for you. > > -- > mike -- 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
Re: [OctDev] Comm package
On Sat, May 12, 2012 at 10:39 AM, Carnë Draug wrote: > On 12 May 2012 14:53, Mike Miller wrote: >> On Sat, May 12, 2012 at 9:48 AM, Carnë Draug >> wrote: >>> On 12 May 2012 14:04, Mike Miller wrote: On Sat, May 12, 2012 at 8:50 AM, Carnë Draug wrote: > On 12 May 2012 13:40, Mike Miller wrote: >> On Sat, May 12, 2012 at 3:34 AM, c. wrote: >>> >>> On 11 May 2012, at 23:18, Mike Miller wrote: >>> Hey Jordi, thanks for getting this moving. I'm no expert on releases, but this isn't working: * filename must match package name, so rename to communications-1.1.1.tar.gz Non-fatal: * would be nice if directory in the tar were the same name instead of "lol" :) * good that you autogen'd the configure script in there, but would be nice to delete autom4te.cache * might as well delete .svnignore files too >>> * also, please remember to generate the html docs with the >>> "generate_package_html" function from the "generate_html" package >>> and post them as well. >> >> Yes, did all that including the html docs and that is up on the >> package release forum now. > > Yes, I see it now. You forgot to update the date of release. It's ok, > I fixed that on my side. What I noticed is that communications now no > longer has marcumq because it moved into signal. I should make a new > release of signal so that there's no period without that function > available. Thanks, I realized that too about the function moving, might as well put out what we have now. I just added a NEWS item for what I've changed in signal. >>> >>> I found a problem with signal because of the circular dependency with >>> communications. While they can be installed at the same time, as soon >>> as one tries to load them it fails with a max_recursion_depth exceeded >>> error. This can be work around with pkg load -nodeps but that should >>> not be an option for a release. Any thoughts? >> >> I let you add it at the time but I thought it might be a problem :) >> Honestly I think bitrevorder should be rewritten to not use the >> communications functions. You could put it out as it was, without the >> dependency, and we'd be no worse than before, and in the future I'd >> like to fix it to get rid of the bi2de/de2bi calls. > > You're right, I didn't foresaw any other problems aside the install. > About fixing this, it just occured to me that I can always make those > 2 functions subfunctinos to bitrevorder. It's not the cleanest option > but seems better than not listing the dependency. What do you think? Just pulled your change that does that, looks good, I think signal should be good to go now. -- mike -- 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
Re: [OctDev] Comm package
On 12 May 2012 15:58, Mike Miller wrote: > On Sat, May 12, 2012 at 10:39 AM, Carnë Draug > wrote: >> On 12 May 2012 14:53, Mike Miller wrote: >>> On Sat, May 12, 2012 at 9:48 AM, Carnë Draug >>> wrote: On 12 May 2012 14:04, Mike Miller wrote: > On Sat, May 12, 2012 at 8:50 AM, Carnë Draug > wrote: >> On 12 May 2012 13:40, Mike Miller wrote: >>> On Sat, May 12, 2012 at 3:34 AM, c. wrote: On 11 May 2012, at 23:18, Mike Miller wrote: > Hey Jordi, thanks for getting this moving. I'm no expert on releases, > but this isn't working: > * filename must match package name, so rename to > communications-1.1.1.tar.gz > Non-fatal: > * would be nice if directory in the tar were the same name instead > of "lol" :) > * good that you autogen'd the configure script in there, but would > be nice to delete autom4te.cache > * might as well delete .svnignore files too * also, please remember to generate the html docs with the "generate_package_html" function from the "generate_html" package and post them as well. >>> >>> Yes, did all that including the html docs and that is up on the >>> package release forum now. >> >> Yes, I see it now. You forgot to update the date of release. It's ok, >> I fixed that on my side. What I noticed is that communications now no >> longer has marcumq because it moved into signal. I should make a new >> release of signal so that there's no period without that function >> available. > > Thanks, I realized that too about the function moving, might as well > put out what we have now. I just added a NEWS item for what I've > changed in signal. I found a problem with signal because of the circular dependency with communications. While they can be installed at the same time, as soon as one tries to load them it fails with a max_recursion_depth exceeded error. This can be work around with pkg load -nodeps but that should not be an option for a release. Any thoughts? >>> >>> I let you add it at the time but I thought it might be a problem :) >>> Honestly I think bitrevorder should be rewritten to not use the >>> communications functions. You could put it out as it was, without the >>> dependency, and we'd be no worse than before, and in the future I'd >>> like to fix it to get rid of the bi2de/de2bi calls. >> >> You're right, I didn't foresaw any other problems aside the install. >> About fixing this, it just occured to me that I can always make those >> 2 functions subfunctinos to bitrevorder. It's not the cleanest option >> but seems better than not listing the dependency. What do you think? > > Just pulled your change that does that, looks good, I think signal > should be good to go now. Yes. However, when the next release of image comes out there will be a problem. Next release will be dependent on signal and signal is dependent on image because of marcumq... 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
[OctDev] New releases of communications (1.1.1) and signal (1.1.3)
Hi everybody new releases of the communications and signal packages have just been made. Have fun 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
[OctDev] multiple instances of the same package
I have some packages installed globally via apt-get and some installed locally with pkg install -local. Is this expected to work with more than one instance of the same package name, i.e. only the one with the highest version is used? I locally installed the new signal and communications, this seems to work for signal but not for communications. Any ideas where I can look for what's happening here? octave:24> pkg list Package Name| Version | Installation directory +-+--- communications *| 1.1.1 | /home/mike/octave/communications-1.1.1 communications *| 1.1.0 | /usr/share/octave/packages/communications-1.1.0 control *| 2.3.50 | /usr/share/octave/packages/control-2.3.50 generate_html *| 0.1.4 | /home/mike/octave/generate_html-0.1.4 image *| 1.0.15 | /usr/share/octave/packages/image-1.0.15 miscellaneous *| 1.1.0 | /usr/share/octave/packages/miscellaneous-1.1.0 optim *| 1.0.17 | /usr/share/octave/packages/optim-1.0.17 signal *| 1.1.3 | /home/mike/octave/signal-1.1.3 specfun *| 1.1.0 | /usr/share/octave/packages/specfun-1.1.0 struct *| 1.0.9 | /usr/share/octave/packages/struct-1.0.9 -- mike -- 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
Re: [OctDev] Comm package
On 12 May 2012 03:34, c. wrote: > > On 11 May 2012, at 23:18, Mike Miller wrote: > >> Hey Jordi, thanks for getting this moving. I'm no expert on releases, >> but this isn't working: >> * filename must match package name, so rename to communications-1.1.1.tar.gz >> Non-fatal: >> * would be nice if directory in the tar were the same name instead of "lol" >> :) >> * good that you autogen'd the configure script in there, but would >> be nice to delete autom4te.cache >> * might as well delete .svnignore files too > * also, please remember to generate the html docs with the > "generate_package_html" function from the "generate_html" package > and post them as well. Thanks for the quality control and the package upload, guys. I'm just glad another Octave package got fixed. - Jordi G. H. -- 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
