Re: [OctDev] main ported to the package system

[David B. <Dav...@mo...>]

S=C3=B8ren Hauberg wrote:

>I've copied the admin directories to the packages that needed the
>octlink.sh script. If I forgot to copy it into a package that actually
>needs the script, then I've made a mistake. Which packages are giving
>you problems because octlink.sh is missing?
>
>I've not been involved in octave long enough to actually know what these
>scripts does. But from what you are saying, I get the impression that
>octlink.sh needs to be removed from the individual packages and replaced
>by PKG_ADD files.
> =20
>

octlink.sh was a hack that allowed support of both symbolic links and
the use of the octave autoload function on systems that supportted it.
Version of octave later than 2.9.4 all support autoload and so
octlink.sh is no longer needed as such as what is done in this script
should be done for all symbolic links. However, with the way the pkg
build system seems to work this means it needs to be done on a package
by package basis (Soren comments)

This stuff hooks into the admin/mkpkgadd script. Again it doesn't seem
obvious to me how we can make mkpkgadd and octlink part of pkg.m rather
than the individual packages. Searching the *.m and *.cc files for
PKG_ADD commands is easy enough, but the treatment of the symbolic links
needs to be done on a package by package basis.

Perhaps we can make a pkg/src/symlinks and pkg/inst/symlinks file in the
package manager, that includes pairs like

gf glu
gf greal

etc, which repesent "ln -s gf.oct glu.oct". The pkg.m script can then
convert these to

autoload ("glu", which ("gf"));
autoload ("greal", which ("gf"));

in the PKG_ADD file. This of course requires a small modification the
pkg.m. So Soren your thoughts on this are necessary.. I'll try to
propose something since this is blocking my porting of the
communications toolbox.

D.

>S=C3=B8ren
>
>man, 21 08 2006 kl. 16:22 +0200, skrev David Bateman:
> =20
>
>>Ok, another nasty problem is that the admin/octlink.sh script is not
>>copied to the pkg src/ directories. Perhaps as teh package manager is
>>only in versions of octave which have the autoload function, this can
>>all be simplified, as only the .octlink fashion of dealing with the
>>files needs to be treated. That is we should probably generate the
>>appropriate PKD_ADD file directly rather than use octlink.sh.. This
>>problem occurs wherecer symbolic links are used in octave-forge. Its
>>vital that autoload is used if possible to allow significant reduction
>>in binary size especially for cygwin and mingw platforms...
>>
>>I'll work out a solution for the communications toolbox and propose it.
>>
>>D.
>>
>>
>>   =20
>>
>
>
>
> =20
>


--=20
David Bateman                                Dav...@mo...
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph)=20
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob)=20
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax)=20

The information contained in this communication has been classified as:=20

[x] General Business Information=20
[ ] Motorola Internal Use Only=20
[ ] Motorola Confidential Proprietary