[Pkg-octave-devel] Packaging Octave 3.8

[Mike Miller]

On Wed, Dec 11, 2013 at 15:44:50 +0100, Sébastien Villemot wrote:
> Le mercredi 11 décembre 2013 à 09:03 -0500, Mike Miller a écrit :
>> The new octave-gui package will contain /usr/bin/octave-gui and depend
>> on the octave package. It's an added layer instead of an alternative.
>
> Sorry I just realized that, with your proposed splitting scheme (the GUI
> in octave-gui), it is indeed not necessary to modify
> reverse-dependencies.
>
> However how do you see that evolve when the GUI becomes the default with
> Octave 4.0? Will /usr/bin/octave be linked against liboctgui?

Yes, you're right of course. I agree the intention of upstream is that
the GUI will become the default in 4.0 and the CLI mode will be by
request only or in non-X environments. With my proposal I was focusing
on this release where the GUI is optional, but the upstream plan is
for this to be a short-lived transitional release.

So yes, I agree it does make sense from the long-term point of view
for the octave binary package to provide the octave-gui executable.

In your plan, what do you propose to do with the oct-files that are
currently in the octave package? Because both octave and octave-cli
need those files, either octave-cli would have to depend on octave, in
which case there is again no need for an or-dependency, or the
oct-files would also have to be split into a new package.

-- 
mike