Re: Flummoxed again by Octave

2016-10-27 Thread Marius Schamschula
Jerry,

To list the installed versions of octave-devel:

post select octave

to select a particular version, e.g. octave-devel-rc:

sudo port select octave octave-devel-rc

On Oct 27, 2016, at 5:59 PM, list_em...@icloud.com wrote:

>> 
>> On Oct 27, 2016, at 1:29 PM, Marius Schamschula  
>> wrote:
>> 
>> Jerry,
>> 
>> If you want to use octave packages with octave-devel*, you need to use 
>> octave select. Otherwise mkoctfile (which is needed to build octave 
>> packages) cannot be found, and MacPorts will proceed to install octave.
> 
> I can’t figure out how to use octave select or octave_select.
> Jerry
>> 
>> On Oct 27, 2016, at 3:11 PM, list_em...@icloud.com wrote:
>> 
>>> I recently did a fresh installation of MacPorts. I then installed 
>>> octave-devel because the version given for it is 4.1.0+, more recent than 
>>> that for octave the version of which is given as 4.0.3_1.
>>> 
>>> I then did 
>>> 
>>> sudo port install octave-signal
>>> 
>>> which immediately began trying to install octave 4.0.3_1. I control-C-ed 
>>> out of that process after a few seconds after I realized what was 
>>> happening. Now I have these questions:
>>> 
>>> (1) Can I do a "sudo port clean --dist octave" to get rid of any junk that 
>>> was installed by the aborted octave installation?
>>> 
>>> (2) Can I install octave packages such as octave-signal into octave-devel? 
>>> If so, how? Does this involve using octave_select?
>>> 
>>> (3) If I need to revert to octave 4.0.3_1, how do I remove _all_ of 
>>> octave-devel. In the past I have found that uninstalling ports doesn’t 
>>> return my disk usage to what it was before installing, usually by several 
>>> GB. I want to keep a lean and clean MacPorts installation.
>>> 
>>> Thanks as usual.
>>> 
>>> Jerry
>>> ___
>>> macports-users mailing list
>>> macports-users@lists.macosforge.org
>>> https://lists.macosforge.org/mailman/listinfo/macports-users
>> 
>> Marius
>> --
>> Marius Schamschula
>> 
>> 
>> 
>> 
> 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

Marius
--
Marius Schamschula




___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: Flummoxed again by Octave

2016-10-27 Thread list_email

> On Oct 27, 2016, at 1:29 PM, Marius Schamschula  wrote:
> 
> Jerry,
> 
> If you want to use octave packages with octave-devel*, you need to use octave 
> select. Otherwise mkoctfile (which is needed to build octave packages) cannot 
> be found, and MacPorts will proceed to install octave.

I can’t figure out how to use octave select or octave_select.
Jerry
> 
> On Oct 27, 2016, at 3:11 PM, list_em...@icloud.com 
>  wrote:
> 
>> I recently did a fresh installation of MacPorts. I then installed 
>> octave-devel because the version given for it is 4.1.0+, more recent than 
>> that for octave the version of which is given as 4.0.3_1.
>> 
>> I then did 
>> 
>> sudo port install octave-signal
>> 
>> which immediately began trying to install octave 4.0.3_1. I control-C-ed out 
>> of that process after a few seconds after I realized what was happening. Now 
>> I have these questions:
>> 
>> (1) Can I do a "sudo port clean --dist octave" to get rid of any junk that 
>> was installed by the aborted octave installation?
>> 
>> (2) Can I install octave packages such as octave-signal into octave-devel? 
>> If so, how? Does this involve using octave_select?
>> 
>> (3) If I need to revert to octave 4.0.3_1, how do I remove _all_ of 
>> octave-devel. In the past I have found that uninstalling ports doesn’t 
>> return my disk usage to what it was before installing, usually by several 
>> GB. I want to keep a lean and clean MacPorts installation.
>> 
>> Thanks as usual.
>> 
>> Jerry
>> ___
>> macports-users mailing list
>> macports-users@lists.macosforge.org 
>> 
>> https://lists.macosforge.org/mailman/listinfo/macports-users
> 
> Marius
> --
> Marius Schamschula
> 
> 
> 
> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: Flummoxed again by Octave

2016-10-27 Thread Brandon Allbery
On Thu, Oct 27, 2016 at 4:11 PM,  wrote:

> I recently did a fresh installation of MacPorts. I then installed
> octave-devel because the version given for it is 4.1.0+, more recent than
> that for octave the version of which is given as 4.0.3_1.
>

-devel ports are for testing; there is no guarantee of compatibility with
dependents of the stable port version.

(1) Can I do a "sudo port clean --dist octave" to get rid of any junk that
> was installed by the aborted octave installation?
>

--dist removes the source distribution. Other components may be left
behind. Perhaps you want --all, or at least --work --dist --archive.


> (2) Can I install octave packages such as octave-signal into octave-devel?
> If so, how? Does this involve using octave_select?
>

select ports change what shows up on the user's $PATH. They should not
affect installation or maintenance via the port command, and a port which
relied on port select to determine what or where to install would be
considered buggy because it defeats using port select to let the user
switch between different, possibly incompatible, versions of a package.

(3) If I need to revert to octave 4.0.3_1, how do I remove _all_ of
> octave-devel. In the past I have found that uninstalling ports doesn’t
> return my disk usage to what it was before installing, usually by several
> GB. I want to keep a lean and clean MacPorts installation.
>

Uninstall will leave distfiles and downloaded archives behind; this is a
use case for `port clean --dist` (possibly also with --archive) that you
mentioned above. If you are regularly seeing additional space usage after
removing installed files and distfiles, make sure you have not configured
macports.conf to retain work directories or build log files (either of
which you might change in order to debug buggy ports).

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Flummoxed again by Octave

2016-10-27 Thread list_email
I recently did a fresh installation of MacPorts. I then installed octave-devel 
because the version given for it is 4.1.0+, more recent than that for octave 
the version of which is given as 4.0.3_1.

I then did 

sudo port install octave-signal

which immediately began trying to install octave 4.0.3_1. I control-C-ed out of 
that process after a few seconds after I realized what was happening. Now I 
have these questions:

(1) Can I do a "sudo port clean --dist octave" to get rid of any junk that was 
installed by the aborted octave installation?

(2) Can I install octave packages such as octave-signal into octave-devel? If 
so, how? Does this involve using octave_select?

(3) If I need to revert to octave 4.0.3_1, how do I remove _all_ of 
octave-devel. In the past I have found that uninstalling ports doesn’t return 
my disk usage to what it was before installing, usually by several GB. I want 
to keep a lean and clean MacPorts installation.

Thanks as usual.

Jerry
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users