Clemens Buchacher wrote: > On Sun, Mar 25, 2012 at 04:58:26PM +0200, c. wrote: >> >> I don't think this completely solves the issue we are dealing with, >> if all files are installed in the same path a PKG_ADD file like this: >> >> http://geopdes.svn.sourceforge.net/viewvc/geopdes/trunk/geopdes_base/PKG_ADD?revision=456&view=markup >> >> should already be enough to deal with the problem. > > This is what we started out with. > >> the problem is that the installation path for architecture dependent >> and indepent file could be completely different. I think this is for >> example the case in the default configuration for Octave on Debian and >> o widows. > > And this is what the suggested function solves. The architecture > dependent files can be found in the same directory as PKG_ADD, and the > architecture indepdenent files can be found using pkg("list"). With > Philip's comments I realized that the latter can be done with just this: > > pkglist = pkg ("list"); > ind = find (cellfun(@(x) strcmp(x.name, "geometry"), pkglist), 1, "first"); > if ind > dir = pkglist{ind}.dir; > endif > > So maybe a separate function is overkill.
It is really nice to be able to get info on a package by a function call (that functionality still lacks). A separate function, however small, would also be a bit "cleaner" as the maintainer doesn't have to worry about clearing used variables (pkglist, ind, dir). There used to be a few PKG_ADDs that left various cruft after starting Octave (incl. the io pkg's PKG_ADD, now fixed). Philip ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
