On 12 May 2012 15:58, Mike Miller <mike.t.mil...@gmail.com> wrote: > On Sat, May 12, 2012 at 10:39 AM, Carnë Draug <carandraug+...@gmail.com> > wrote: >> On 12 May 2012 14:53, Mike Miller <mike.t.mil...@gmail.com> wrote: >>> On Sat, May 12, 2012 at 9:48 AM, Carnë Draug <carandraug+...@gmail.com> >>> wrote: >>>> On 12 May 2012 14:04, Mike Miller <mike.t.mil...@gmail.com> wrote: >>>>> On Sat, May 12, 2012 at 8:50 AM, Carnë Draug <carandraug+...@gmail.com> >>>>> wrote: >>>>>> On 12 May 2012 13:40, Mike Miller <mike.t.mil...@gmail.com> wrote: >>>>>>> On Sat, May 12, 2012 at 3:34 AM, c. <carlo.defa...@gmail.com> 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
