Hi Johan, Put the your folder wherever it feels natural for you. I will adapt the script to handle that. The only requirement is that Inside your folder you have the structure of a package. So, for you it means you just drop your package where you want it. I will then merge the "capitalized" files (INDEX, DESCRIPTION, etc...) and the Makefile, if you have one.
I am Glad to hear we are on the move. JPi 2011/9/29 Johan Beke <johanb...@hotmail.com>: > Juan, > > I ll move my project into the mechanics (although my package is more for > static structural analysis but that does not bother me) . However, I do not > clearly see where I will put my files. I just move my folder ocframe into > your folder. On my computer I just got the svn structure which is: > > octave-forge > |_ main > |_ mechanics > |_ inst > > Do you mean that I must do the following? > > octave-forge > |_ main > |_ mechanics > |_ inst > |_ ocframe > > where ocframe contains the contents of my inst folder? > > Anyway, I took a quick look at my code and I 'm thinking of rewriting it > (faster version which as prototype for a 3D). > > Greetings, > > Johan > >> Date: Thu, 29 Sep 2011 12:00:09 +0200 >> Subject: Package ocframe >> From: carba...@ifi.uzh.ch >> To: carandraug+...@gmail.com; johanb...@hotmail.com; >> octave-dev@lists.sourceforge.net >> >> Dear Johan >> >> ===== >> @maintainers: Description text of "package/pre_install.m" in >> http://octave.sourceforge.net/developers.html should change to >> "This is an optional **function** that is run prior to the >> installation of a package. " >> I do not known if applies to the other functions/scrtips, but I guess it >> does. >> === >> >> I just wrote a scr ipt that will allows us (in case you accept the >> merging) to have ocframe as a more-or-less independent subpackage of >> mechanics (though to install you need to install mechanics) >> >> The structure is as follows >> mechanics >> ├── COPYING >> ├── DESCRIPTION >> ├── doc >> │ └── NEWS >> ├── INDEX >> ├── src >> ├── inst >> │ ├── private >> │ ├── <my files mFiles> >> │ └── ocframe >> │ ├── src >> │ ├── inst >> │ │ └── private >> │ └── <your files mFiles> >> └── pre_install.m >> >> So ocframe would be a subfolder of inst. When installed, the structure >> is lost, this is just for maintenance. >> (It is easy to change the structure to put ocframe as a subfolder of >> mechanics instea d of mechanics/inst). >> >> Here is an example of the pre_install.m function >> http://agora.panocha.org.mx/snippet/SkIg/ >> >> You would need to add "ocframe" to the subfld cell in line 6. >> >> If you accept (and if needed) pre_install.m has to be enhanced to >> merge any Makefile you may have in ocframe/src/. >> Similarly, so far the file INDEX has to be maintained manually, >> however pre_install could handle the merging. >> >> Let me known >> >> -- >> M. Sc. Juan Pablo Carbajal >> ----- >> PhD Student >> University of Zürich >> http://ailab.ifi.uzh.ch/carbajal/ > -- M. Sc. Juan Pablo Carbajal ----- PhD Student University of Zürich http://ailab.ifi.uzh.ch/carbajal/ ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
