octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issues with build Fedora RPMs of octave packages


From: Michael Goffioul
Subject: Re: Issues with build Fedora RPMs of octave packages
Date: Fri, 21 Sep 2007 09:56:25 +0200

On 9/21/07, David Bateman <address@hidden> wrote:
> > Why not get the path inserted at install time?  That's essentially the
> > hack I've done to my octave-forge package, but it would be better if
> > this could get supported automatically.
> >
> > Source PKG_ADD would look something like:
> >
> > autoload("funct","@OCTPATH@/myfuncts.oct");
> >
> > and @OCTPATH@ gets substituted at install time.
>
>
> What does install time mean in this context? If a user runs "pkg install
> ..." should it file in the path. Yes. If you are fedora packager run it,
> then no.. This is problematic... I think the best option is to make
> autoload check in the same directory as the function or script
> containing the autoload command first and then check the user path.
> Though this is a less important change than the LOCALAPIFILEDIR change..

I'm also not in favour of such change as this would make PKG_ADD
files not relocatable.

Michael.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]