On 9 January 2012 16:46, Josef Leydold <josef.leyd...@wu.ac.at> wrote: > On Mon, Jan 09, 2012 at 04:27:32PM +0000, Carnė Draug wrote: >> On 4 January 2012 14:23, Josef Leydold <josef.leyd...@wu.ac.at> wrote: >> > Thanks for your reply. >> > >> > I have put the sources on our webserver: >> > >> > http://statmath.wu.ac.at/unuran/unuran-1.9.devel.tar.gz >> > http://statmath.wu.ac.at/unuran/octunuran.cc >> > http://statmath.wu.ac.at/unuran/octunuran.Makefile >> > >> > I have put all soures into the file octunuran.cc and have used symlinks >> > (see octunuran.Makefile) to make the different oct functions available >> > in octave (this should be replaced by corresponding entries in >> > PKG_ADD). >> > >> > The source file is rather long and should be split into smaller ones >> > (at least I would do so with C files). >> > >> > When one wants to test the package do the following: >> > >> > 1. Install unuran-1.9.devel.tar.gz (notice that this is a development >> > snapshot of the UNU.RAN library that includes some new functions >> > that are required for octunuran). >> > >> > 2. compile the oct file(s) and create symlinks (see octunuran.Makefile). >> > >> > 3. Before using any other command from this package run >> > unuran_config(); >> > (This statement will be put into file PKG_ADD.) >> > >> > So if you are interested in the package please take a look. >> > Comments are welcome. >> >> Hi Josef >> >> as Arno as already mentioned, octave-forge is indeed the right place. >> Can you make an actual octave package? The kind that is installed with >> the "pkg install" command? It's really easy, just place .m and C++ >> files in a inst/ and src/ directories respectively. Then create a >> COPYING file (with the license), a DESCRIPTION file (with version, >> package name, etc), a Makefile (seems you'll need one). I'll recommend >> that you also create a NEWS file (packages from octave-forge can be >> installed without need of manual download from the user but octave >> will keep this file for users to read). See the already existing >> octave package for examples. This links shows the image package >> >> http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/main/image/ >> >> Again, as Arno as suggested, it's probably better to have a new >> package for this code (instead of adding your code another one) since >> you say that it's dependent on a library difficult to build on other >> systems. Do you have a better name for it? unuran is not very >> descriptive (I know we already have some packages with rather cryptic >> names but that doesn't mean we should repeat this). >> >> Yet again, as Arno has said, the UNU.RAN library should be distributed >> separately. >> >> On 9 January 2012 11:02, Olaf Till <olaf.t...@uni-jena.de> wrote: >> > For this, you should either start a new thread or >> > prepend something like "Carnė please read" to the subject so that your >> > request does not get overlooked. >> >> No need to do this at the time. I've just been specially slow after >> Christmas but threads haven't been ignored. I have 59 unread octave >> mails of stuff that I'll try to do on the next few of days. >> >> Carnė >> > > Hi Carne, > > Yes I can try to create a package. However, before a possible release > I have to fix some issues in some other stuff. > I just have a question: > > Is it possible to add something like a help page for the entire > library or some additional documentation similar to > R's vignette? > > Concering the name: > > UNU.RAN is an abbreviation for > Universal NonUniform RANdom variate generators > > Do you have better names in mind? > (I do not want to call it just unuran since then I have two projects > with the same name.) > > Josef
Please avoid top posting and always include the mailing list on the list of senders (I'm CC'ing the maling list now). I am not familiar with R's vignette but it's possible to include documentation for an entire package by including it into the doc/ directory (see the java package for an example). This documentation can then be accessed with the doc function. Also, we have a wiki page where packages can have their documentation ( http://octave.org/wiki/index.php?title=Category:Packages ). Personally I prefer the wiki since it makes contribution by users easier and a documentation should be easily created from the wiki source with a script. No, I don't have a better name. However, it would be nice if you choose anything not very cryptic. When users are checking the list of packages, what they see is just the list of packages names. Carnë ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
