Re: Managing multiple TeXLive installations

2016-02-26 Thread Mojca Miklavec 
On 27 February 2016 at 00:21, Jerry wrote:
> I am struggling with two different installations of TeXLive.
>
> One is a 2013 version from TUG which was a binary installed mostly into 
> /usr/local/texlive but with GUI apps in /Applications/TeX/.

2013 is relatively old.

> The other is MacPorts 2015 version...
>
> $ port installed *texlive*
> The following ports are currently installed:
>   texlive-basic @30847_0+doc
>   texlive-basic @34245_0+doc
>   texlive-basic @37485_0+doc (active)
>   texlive-bin @2013_5+x11
>   texlive-bin @2014_1+x11
>   texlive-bin @2014_9+x11
>   texlive-bin @2015_8+x11 (active)
>   texlive-common @2013_0
>   texlive-common @2014_0
>   texlive-common @2015_0 (active)
>   texlive-fonts-recommended @36916_0+doc (active)
>   texlive-latex @30738_0+doc
>   texlive-latex @34192_0+doc
>   texlive-latex @37361_0+doc (active)
>
> I want to simplify and save space and reduce the possibility of conflicts.

You can also run "sudo port uninstall inactive" or "sudo port unintall
inactive and 'texlive*'" to save extra space. I just wanted to add
that I have multiple installations of TeX (MacTeX 2014, 2015), TeXLive
from MacPorts, a standalone ConTeXt installation, ...

In System Preferences you most likely have an icon for "TeX
Distribution". It is possible that you can select MacPorts from there
(I'm not sure about the exact history of when MacPorts was
added/removed) and then all the nice GUI apps would automatically
switch to using TeX Live from MacPorts as well (it's mostly just a
symlink /usr/texbin and some other link on 10.11, but if you have
version 2013, it's probably /usr/texbin).

Other than that it all depends on PATH settings. Whatever
"latex/pdftex/kpsewhich/..." comes first in PATH will also be used.
I'm not sure how exactly LyX deals with paths though because it's not
a command-line program.

> However, the 2013 TUG version installed the very nice collection of GUI apps 
> in /Applications/TeX which I would like to use especially BibDesk. When I 
> look in /Applications/MacPorts there are no corresponding programs.

Many programs are standalone apps that are not really part of TeX
Live, but are packaged for convenience by the person who creates
MacTeX.

You can download BibDesk from http://bibdesk.sourceforge.net/. And
given that the sources are available, it should be feasible to create
a package in MacPorts as well. The same is true for most other apps
that come bundled with MacTeX.

> Can I delete /usr/local/texlive/2013 and keep the GUI apps in 
> /Applications/TeX and if so, how would I keep the GUIs updated?

Sure. Just do "sudo rm -rf /usr/local/texlive/2013" (or perhaps "sudo
mv /usr/local/texlive /usr/local/texlive-backup"). You will probably
also want to remove /usr/texbin from PATH or perhaps point /usr/texbin
to /opt/local/bin.

After that you might need to adjust paths in individual programs. I
don't use BibDesk, so I'm not sure what has to be done there, but in
case that it actually needs TeX and doesn't just output .bib files I'm
sure there exists some setting to point it to the desired version of
TeX.

> Or is there a way to get the GUI apps to be installed by MacPorts, presumably 
> into /Applications/MacPorts? I don't see a GUI variant.

There is no +gui variant or will ever be one. Someone would have to
prepare build rules for these individual programs. There are some
attempts like this one:
https://trac.macports.org/ticket/16055
but someone motivated would have to step in to package all of them.

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

xemacs 21.4.22_11 load path shadows

2016-02-26 Thread Eric Smith 
Dear all:

I have recently installed the port xemacs @21.4.22_11 on two different 
machines, and am having trouble with load path shadowing, which I don't find 
mentioned anywhere in either bug lists or mailing lists.

One machine is an older mini (mid 2011) running Lion, and this xemacs is an 
upgrade from 21.4.22_9.  All earlier versions are inactive, and I cannot 
activate them without forcing due to a ctags 5.8.2 dependency.

The other machine is a new (clean) 2015 macbook pro running El Capitan, on 
which this is the first set of macports installs, and the only copy of xemacs.  
 

The problem is the same on both machines, so I assume it is not due to a 
version overlap, or specific to either Lion or El Capitan.

The problem is that when opening any file, I now get a split window, announcing 
a set of warnings from Autoload, of the form 

(1) (warning/warning) Autoload error in: 
/opt/local/lib/xemacs/xemacs-packages/lisp/zenirc/auto-autoloads:
Already loaded

(and 129 more for various other files)

These are explained in the xemacs FAQ Q 2.5.7 at 
http://www.xemacs.org/Documentation/21.5/html/xemacs-faq_3.html#SEC122
but not what to do about them.

If I give xemacs the command
M-x list-load-path-shadows
five load-path shadowings are reported as 

/opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/cedet-common/working hides 
/opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/semantic/working
/opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/cedet-common/sformat hides 
/opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/semantic/sformat
/opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/xemacs-base/easy-mmode hides 
/opt/local/lib/xemacs-21.4.22/lisp/easy-mmode
/opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/build/build-report hides 
/opt/local/lib/xemacs-21.4.22/lisp/build-report
/opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/apel/alist hides 
/opt/local/lib/xemacs-21.4.22/lisp/alist

Looking at each of these pairs, they are all normal files (not symlinks)

-rw-r--r--  1 root  admin  23686 Nov 27  2007 
/opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/cedet-common/working.el
-rw-r--r--  1 root  admin  23767 Aug  6  2002 
/opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/semantic/working.el

-rw-r--r--  1 root  admin  13799 Nov 27  2007 
/opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/cedet-common/sformat.el
-rw-r--r--  1 root  admin  13796 Aug 12  2002 
/opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/semantic/sformat.el

-rw-r--r--  1 macports  admin  22285 Dec 31  2008 
/opt/local/lib/xemacs-21.4.22/lisp/easy-mmode.el
-rw-r--r--  1 root  admin  22480 Nov  8  2004 
/opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/xemacs-base/easy-mmode.el

-rw-r--r--  1 macports  admin  19420 May  9  2001 
/opt/local/lib/xemacs-21.4.22/lisp/build-report.el
-rw-r--r--  1 root  admin  20112 Oct  2  2009 
/opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/build/build-report.el

-rw-r--r--  1 macports  admin  3136 Apr 13  2001 
/opt/local/lib/xemacs-21.4.22/lisp/alist.el
-rw-r--r--  1 root  admin  2989 Aug 18  2009 
/opt/local/lib/xemacs-21.4.22/xemacs-packages/lisp/apel/alist.el

(plus .elc versions of the above files)

All properties of each of these files is identical on the two installations, so 
I assume that this problem is created locally by this port.

Sorry if this is a dumb question.  There must be vast numbers of users of this 
port, so I don't know why I haven't seen it mentioned anywhere.

Thanks for help,

Eric





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

Re: Audacity build question. for Ticket #47189

2016-02-26 Thread Ryan Schmidt 

On Feb 26, 2016, at 5:20 PM, Eneko Gotzon wrote:
> 
> Sorry if I'm mistaken, I have not been able to follow this thread.
> 
> On Fri, Feb 26, 2016 at 5:08 PM, Mojca Miklavec  wrote:
> sudo port install audacity
> 
> Audacity is not available for installation on MacPorts, isn't?

A ticket was filed a long time ago (see subject), and was committed to the 
repository recently.


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

Managing multiple TeXLive installations

2016-02-26 Thread Jerry 
I am struggling with two different installations of TeXLive.

One is a 2013 version from TUG which was a binary installed mostly into 
/usr/local/texlive but with GUI apps in /Applications/TeX/.

The other is MacPorts 2015 version...

$ port installed *texlive*
The following ports are currently installed:
  texlive-basic @30847_0+doc
  texlive-basic @34245_0+doc
  texlive-basic @37485_0+doc (active)
  texlive-bin @2013_5+x11
  texlive-bin @2014_1+x11
  texlive-bin @2014_9+x11
  texlive-bin @2015_8+x11 (active)
  texlive-common @2013_0
  texlive-common @2014_0
  texlive-common @2015_0 (active)
  texlive-fonts-recommended @36916_0+doc (active)
  texlive-latex @30738_0+doc
  texlive-latex @34192_0+doc
  texlive-latex @37361_0+doc (active)

I want to simplify and save space and reduce the possibility of conflicts. (My 
use is mostly through LyX--not the MacPorts version but typically a dev version 
from lyx.org, and I am currently helping to chase down some LyX-TeX problems.) 
Since the MacPorts TeXLive version is here to stay as apparently it is needed 
by some other port, the reasonable thing to do would seem to be to get rid of 
the 2013 TUG version by trashing stuff. However, the 2013 TUG version installed 
the very nice collection of GUI apps in /Applications/TeX which I would like to 
use especially BibDesk. When I look in /Applications/MacPorts there are no 
corresponding programs.

Can I delete /usr/local/texlive/2013 and keep the GUI apps in /Applications/TeX 
and if so, how would I keep the GUIs updated? Or is there a way to get the GUI 
apps to be installed by MacPorts, presumably into /Applications/MacPorts? I 
don't see a GUI variant.

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

Re: Audacity build question. for Ticket #47189

2016-02-26 Thread Eneko Gotzon 
Sorry if I'm mistaken, I have not been able to follow this thread.

On Fri, Feb 26, 2016 at 5:08 PM, Mojca Miklavec  wrote:

> sudo port install audacity


Audacity is not available for installation on MacPorts, isn't?

-- 
Eneko Gotzon Ares
enekogot...@gmail.com
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Spawning ping for packages.macports.org failed

2016-02-26 Thread John Oliver 
On Fri, Feb 26, 2016 at 02:52:33PM -0500, Daniel J. Luke wrote:
> ok.
> 
> Try:
> 
> dig @131.215.125.1 packages.macports.org
> 
> and
> 
> dig @131.215.254.100 packages.macports.org
> 
> to help rule out basic dns problems.

I'd suggest:

dig @131.215.125.1 any packages.macports.org

Sometimes, IPv4 vs. IPv6 is the issue, or maybe there's something weird
about a CNAME and what it resolves to.

-- 
***
* John Oliver http://www.john-oliver.net/ *
* *
***
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Spawning ping for packages.macports.org failed

2016-02-26 Thread Daniel J. Luke 
ok.

Try:

dig @131.215.125.1 packages.macports.org

and

dig @131.215.254.100 packages.macports.org

to help rule out basic dns problems.

> On Feb 26, 2016, at 2:15 PM, Adam Mercer  wrote:
> On Feb 26, 2016 09:42, "Daniel J. Luke"  wrote:
> > What does /etc/resolv.conf contain?
> 
> # This file is automatically generated.
> #
> search ligo.caltech.edu ligo.org
> nameserver 131.215.125.1
> nameserver 131.215.254.100


-- 
Daniel J. Luke



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

Re: Spawning ping for packages.macports.org failed

2016-02-26 Thread Adam Mercer 
On Feb 26, 2016 09:42, "Daniel J. Luke"  wrote:

> What does /etc/resolv.conf contain?

# This file is automatically generated.
#
search ligo.caltech.edu ligo.org
nameserver 131.215.125.1
nameserver 131.215.254.100

Cheers

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

Re: Audacity build question. for Ticket #47189

2016-02-26 Thread Mojca Miklavec 
On 26 February 2016 at 18:08, Robert Chalmers wrote:
> Thanks Mojca,
>
> It does compile and install with no problems as you say. However it’s still
> the same 2.1.2 that has it’s own issues (bugs?) that I’m waiting patiently
> to see fixed. But not to worry.

It could be helpful to point those problems out. Are these upstream
issues or something that's only present in MacPorts? I only use the
most basic features, so I'm unlikely to run into problems.

I can imagine that the switch from wxWidgets 2.8 to 3.0 introduced a
number of problems. If you can describe the steps to reproduce them
(either in our tracker or even better upstream), we could at least
test and try to figure out if we know how to fix them.

> I’m pretty impressed by your work getting this to build.

This was done by René, not by me.

> I’d love to have
> the time to get it working under XCode with the XCode build. I started with
> it, but collided with a whole lot of issues…

I didn't even look at it, but from what I understand the Xcode project
has the 10.6 SDK hardcoded and it might become tricky to get it to
build under later OSes. (Official build instructions start with tricks
about how to install an ancient Xcode on your machine.)

What is your main reason/motivation to get the Xcode build working?

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

Re: Audacity build question. for Ticket #47189

2016-02-26 Thread Robert Chalmers 
Thanks Mojca,

It does compile and install with no problems as you say. However it’s still the 
same 2.1.2 that has it’s own issues (bugs?) that I’m waiting patiently to see 
fixed. But not to worry. 
I’m pretty impressed by your work getting this to build. I’d love to have the 
time to get it working under XCode with the XCode build. I started with it, but 
collided with a whole lot of issues…..
anyway, as fate would have it, I’ve reverted to 2.1.1 in production here, 
because editing became a nightmare under 2.1.2, and I’m on a fairly large 
audiobook with another even bigger to follow.

Robert



> On 26 Feb 2016, at 16:08, Mojca Miklavec  wrote:
> 
> On 25 February 2016 at 17:47, Robert Chalmers wrote:
>> Sounds good.
>> 
>> Given that the usual method is
>> 
>> port install
>> 
>> Where will the binary/app/package be installed to…. I’d hate to overwrite my
>> functional Audacity 2.1.1, but other than that I’m happy to be a tester.
> 
> You should already be able to do the usual
>sudo port selfupdate
>sudo port install audacity
> 
> The app gets installed to /Applications/MacPorts/Audacity.app (unless
> you installed MacPorts from source and configured it differently) plus
> a few extra files under /opt/local. I guess your other app is in
> /Applications/Audacity.app, so it shouldn't conflict. And even if it
> would conflict (if you would install manually inside
> /Applications/MacPorts/), MacPorts should throw an error and tell you
> that activation of the port failed.
> 
> Feedback welcome.
> 
> Mojca

Robert Chalmers
rob...@chalmers.com .au  Quantum Radio: 
http://tinyurl.com/lwwddov
Mac mini 6.2 - 2012, Intel Core i7,2.3 GHz, Memory:16 GB. El-Capitan 10.11.  
XCode 7.2.1
2TB: Drive 0:HGST HTS721010A9E630. Upper bay. Drive 1:ST1000LM024 HN-M101MBB. 
Lower Bay




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

Re: Audacity build question. for Ticket #47189

2016-02-26 Thread Mojca Miklavec 
On 25 February 2016 at 17:47, Robert Chalmers wrote:
> Sounds good.
>
> Given that the usual method is
>
> port install
>
> Where will the binary/app/package be installed to…. I’d hate to overwrite my
> functional Audacity 2.1.1, but other than that I’m happy to be a tester.

You should already be able to do the usual
sudo port selfupdate
sudo port install audacity

The app gets installed to /Applications/MacPorts/Audacity.app (unless
you installed MacPorts from source and configured it differently) plus
a few extra files under /opt/local. I guess your other app is in
/Applications/Audacity.app, so it shouldn't conflict. And even if it
would conflict (if you would install manually inside
/Applications/MacPorts/), MacPorts should throw an error and tell you
that activation of the port failed.

Feedback welcome.

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

Re: Spawning ping for packages.macports.org failed

2016-02-26 Thread Daniel J. Luke 
On Feb 26, 2016, at 8:53 AM, Brandon Allbery  wrote:
> On Fri, Feb 26, 2016 at 8:10 AM, Rainer Müller  wrote:
> In particular, do you have a /opt/local/bin/grep which fails to execute?
> 
> I don't think this matters much since it tries the fetch anyway and that also 
> fails to resolve the hostname.

What does /etc/resolv.conf contain?

-- 
Daniel J. Luke



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

Re: Spawning ping for packages.macports.org failed

2016-02-26 Thread Brandon Allbery 
On Fri, Feb 26, 2016 at 8:10 AM, Rainer Müller  wrote:

> In particular, do you have a /opt/local/bin/grep which fails to execute?


I don't think this matters much since it tries the fetch anyway and that
also fails to resolve the hostname.

-- 
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

Re: Spawning ping for packages.macports.org failed

2016-02-26 Thread Adam Mercer 
On Fri, Feb 26, 2016 at 7:10 AM, Rainer Müller  wrote:

> The command would be:
>
> ping -noq -c3 -t3 $host | grep round-trip | cut -d / -f 5

If I run that for packages.macports.org, the first one it says that
fails then I get the following:

builder-osx-1:~ ram$ ping -noq -c3 -t3 packages.macports.org | grep
round-trip | cut -d / -f 5
14.594
builder-osx-1:~ ram$

and then for one of the others:

builder-osx-1:~ ram$ ping -noq -c3 -t3 sea.us.packages.macports.org |
grep round-trip | cut -d / -f 5
31.960
builder-osx-1:~ ram$

which is the output I'd expect

> Did you have any ports installed before? Is the machine really new or
> did you migrate your old installation?

This is a fresh install of OS X (10.11.3, Xcode 7.2.1) and a brand new
installation of MacPorts. I did install MacPorts from source, and not
the installer, using:

$ CFLAGS="-pipe -Os" ./configure --prefix=/opt/local --enable-readline

but I do this on all of my machines.

> In particular, do you have a /opt/local/bin/grep which fails to execute?

builder-osx-1:~ ram$ which grep
/usr/bin/grep
builder-osx-1:~ ram$

Cheers

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

Re: Spawning ping for packages.macports.org failed

2016-02-26 Thread Rainer Müller 
On 2016-02-25 23:29, Adam Mercer wrote:
> From this machine I can ping and contact all the hosts it complains about.

The command would be:

ping -noq -c3 -t3 $host | grep round-trip | cut -d / -f 5

> Any ideas what's going on here?

Did you have any ports installed before? Is the machine really new or
did you migrate your old installation?

In particular, do you have a /opt/local/bin/grep which fails to execute?

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