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 script 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 instead 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/

------------------------------------------------------------------------------
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

Reply via email to