Rafael Laboissiere wrote: > In the process of building the Debian package for fixed, I found a problem > related to PKG_ADD. The files fixed.cc, fsort.m, and fixedpoint.m have > "PKG_ADD:" directives and those end up in the files: > > /usr/lib/octave/packages/fixed-0.7.5/x86_64-pc-linux-gnu-api-v32/PKG_ADD > /usr/share/octave/packages/fixed-0.7.5/PKG_ADD > > The PKG_ADD file present in the top dir of the distributed tarball is then > not installed. However, it contains essential initializations, whithout > which "test fixedpoint" fails. > > In the patch attached below, the initialization code found in the top dir > PKG_ADD file is distributed accross fixed.cc and fixed-var.cc. This makes > the package works for me in Debian. > > This shouldn't happen, as the package manager is supposed to respect both the top level PKG_ADD and those found in the *.m and *.cc files.. It seems to do this correctly on my system and so I don't understand why it doesn't on yours.. In any case I see no reason to keep the toplevel file as it makes more sense to have these autoload commands closer to the functions themselves and the need for the absolute pathname on autoload has been removed so these can be simplified. Its basically laziness that I didn't get rid of this sooner..h
The maling list stripped your patch, but I believe I correctly recreated it and committed it. D. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
