Re: [OctDev] main ported to the package system

[H. <so...@ha...>]

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.

S=C3=B8ren

man, 21 08 2006 kl. 16:22 +0200, skrev David Bateman:
> 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...
>=20
> I'll work out a solution for the communications toolbox and propose it.
>=20
> D.
>=20
>=20