Re: MacPorts missing links

2016-09-13 Thread David Epstein
> On 12 Sep 2016, at 17:39, Lawrence Velázquez  wrote:
>> I should read more documentation on “port select”. I think that “man port” 
>> does not give an adequate explanation, and I would welcome a pointer to 
>> fuller documentation about “port select”.
> 
> The new documentation system has a "port-select" manpage, but I'm not sure if 
> that has been released.
> 
 I agree that some of the select group entry names we've chosen are not 
 optimal in the way in which they differ from the name of the port they 
 provide. It might be a pain to fix that at this late date.
>> 
>> Presumably you have hard-wired this connection between a select group entry 
>> name and some particular Apple binary. How do I find out which Apple binary?
> 
> They're not really hardcoded. It's just that they've been out there for a 
> while, and presumably people are using them.
> 
> The symlinks to be created are described in a *_select port's "base" file.
> https://trac.macports.org/browser/trunk/dports/sysutils/python_select/files/base
> 
> The *_select port itself can create select entries corresponding to the 
> system-provided installations.
> https://trac.macports.org/browser/trunk/dports/sysutils/python_select/Portfile
> 
> The paths to the system files are described in separate files.
> https://trac.macports.org/browser/trunk/dports/sysutils/python_select/files
> 
> vq

You refer above to the “documentation system”. Could you be more explicit? Are 
you referring to something that is part of a MacPorts installation—if so, what 
is the file/directory name—or to an online document—if so what is the web 
address?

I tried “man port-select” and got "No manual entry for port-select"

I had a look at the trac documents you refer to, but I cannot understand them 
or their relevance to my question. They seem to be aimed at someone with more 
competence and understanding.

David

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


Re: MacPorts missing links

2016-09-13 Thread Lawrence Velázquez
> On Sep 13, 2016, at 3:06 AM, David Epstein  
> wrote:
> 
> One thing that seems to be brought out (by the erroneous answer by “port 
> provides ligpng.la")

It's not erroneous, in the sense that libpng.la really does exist and belong to 
the libpng port. The problem, as Ryan had already noted, is that the mechanism 
for deleting .la files that is in the current base release mistakenly leaves 
symlinks behind.

> is that I made a mistake when updating the OS, to have updated my MacPorts 
> installation, rather than reinstalled. I have been hankering after 
> reinstalling, but Ryan persuaded me not to. This seems to be a new bit of 
> evidence that I ought to reinstall

Reinstalling would not help, as Sinan's reply demonstrated. The libpng build 
would again generate libpng16.la and libpng.la, and base would then delete the 
former but not the latter. And you'd be back where you started.

This won't be fixed for you until the next MacPorts release.

vq
Sent from my iPhone
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: MacPorts missing links

2016-09-13 Thread Ryan Schmidt

> On Sep 13, 2016, at 2:06 AM, David Epstein  
> wrote:
> 
> 
>> On 13 Sep 2016, at 03:19, Ryan Schmidt  wrote:
>> 
>> 
>>> On Sep 12, 2016, at 9:08 PM, Brandon Allbery  wrote:
>>> 
>>> On Mon, Sep 12, 2016 at 9:59 PM, Ryan Schmidt  
>>> wrote:
>>> What do you get when you run:
>>> port provides /opt/local/lib/libpng.la
>>> 
>>> They actually provided that earlier:
>>> 
 /opt/local/lib/libpng.la  is provided by: libpng
>> 
>> David provided this information about his installation but Sinan didn't yet.
>> 
>> But you know, not only should /opt/local/lib/libpng.la not exist on 
>> Mavericks or later, it shouldn't be a symlink on any system; it should be a 
>> text file.
>> 
>> If it's a symlink on your system, what's it a symlink to?
> 
> Here is the story from my file system
> Macintosh-2:/<2>lib% pwd
> /opt/local/lib
> Macintosh-2:/<2>lib% ls -l libpng.la
> lrwxr-xr-x  1 root  admin  11  6 Sep 10:13 libpng.la@ -> libpng16.la
> Macintosh-2:/<2>lib% port provides libpng.la
> /opt/local/lib/libpng.la is provided by: libpng
> Macintosh-2:/<2>lib% ls libpng*
> libpng.a@ libpng.la@  libpng16.a
> libpng.dylib@ libpng16.16.dylib*  libpng16.dylib@
> Macintosh-2:/<2>lib% ls -l libpng16.la
> ls: libpng16.la: No such file or directory
> Macintosh-2:/<2>lib% port installed libpng
> The following ports are currently installed:
>  libpng @1.6.21_0
>  libpng @1.6.22_0
>  libpng @1.6.23_0
>  libpng @1.6.25_0 (active)
> 
> This looks to me as though it is saying that Ryan was right. the .la file 
> does not exist, only a shadow of it which presumably won’t cause any harm. 
> One question: why the 6 Sept date. Would my uninstall of python have changed 
> the date on the broken symlink?

Let's forget about the libpng.la problem for now. It is a bug in MacPorts base. 
We fixed it in trunk. It will be in the next release of MacPorts. After that 
release, the fix will make its way to each port as those ports are updated.


> One thing that seems to be brought out (by the erroneous answer by “port 
> provides ligpng.la") is that I made a mistake when updating the OS, to have 
> updated my MacPorts installation, rather than reinstalled. I have been 
> hankering after reinstalling, but Ryan persuaded me not to. This seems to be 
> a new bit of evidence that I ought to reinstall, but I would like Ryan to 
> confirm that he now agrees with this, in the light of the new evidence.

You must have reinstalled MacPorts base after upgrading the OS; IIRC, MacPorts 
will not function if you don't; it will just display an error message telling 
you the OS it was built on doesn't match the OS it's running on and refer you 
to the migration instructions.

If you run "sudo port selfupdate" and "port outdated" now, and it shows no 
ports as outdated, then you're fine. If it shows any ports outdated, update 
them, then you'll be fine. No need to reinstall everything.


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


Re: MacPorts missing links

2016-09-13 Thread Brandon Allbery
On Tue, Sep 13, 2016 at 3:06 AM, David Epstein 
wrote:

> One thing that seems to be brought out (by the erroneous answer by “port
> provides ligpng.la
>
> ") is that I made a mistake when updating the OS, to have updated my
> MacPorts installation,
>

Um, a bunch of us have reported the same errant symlink, and it has already
been explained as a bug in MacPorts base.

-- 
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: MacPorts missing links

2016-09-13 Thread David Epstein

> On 13 Sep 2016, at 03:19, Ryan Schmidt  wrote:
> 
> 
>> On Sep 12, 2016, at 9:08 PM, Brandon Allbery  wrote:
>> 
>> On Mon, Sep 12, 2016 at 9:59 PM, Ryan Schmidt  
>> wrote:
>> What do you get when you run:
>> port provides /opt/local/lib/libpng.la
>> 
>> They actually provided that earlier:
>> 
>>> /opt/local/lib/libpng.la  is provided by: libpng
> 
> David provided this information about his installation but Sinan didn't yet.
> 
> But you know, not only should /opt/local/lib/libpng.la not exist on Mavericks 
> or later, it shouldn't be a symlink on any system; it should be a text file.
> 
> If it's a symlink on your system, what's it a symlink to?

Here is the story from my file system
Macintosh-2:/<2>lib% pwd
/opt/local/lib
Macintosh-2:/<2>lib% ls -l libpng.la
lrwxr-xr-x  1 root  admin  11  6 Sep 10:13 libpng.la@ -> libpng16.la
Macintosh-2:/<2>lib% port provides libpng.la
/opt/local/lib/libpng.la is provided by: libpng
Macintosh-2:/<2>lib% ls libpng*
libpng.a@   libpng.la@  libpng16.a
libpng.dylib@   libpng16.16.dylib*  libpng16.dylib@
Macintosh-2:/<2>lib% ls -l libpng16.la
ls: libpng16.la: No such file or directory
Macintosh-2:/<2>lib% port installed libpng
The following ports are currently installed:
  libpng @1.6.21_0
  libpng @1.6.22_0
  libpng @1.6.23_0
  libpng @1.6.25_0 (active)

This looks to me as though it is saying that Ryan was right. the .la file does 
not exist, only a shadow of it which presumably won’t cause any harm. One 
question: why the 6 Sept date. Would my uninstall of python have changed the 
date on the broken symlink?

One thing that seems to be brought out (by the erroneous answer by “port 
provides ligpng.la") is that I made a mistake when updating the OS, to have 
updated my MacPorts installation, rather than reinstalled. I have been 
hankering after reinstalling, but Ryan persuaded me not to. This seems to be a 
new bit of evidence that I ought to reinstall, but I would like Ryan to confirm 
that he now agrees with this, in the light of the new evidence.

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


Re: MacPorts missing links

2016-09-12 Thread Al Varnell

On Sep 12, 2016, at 8:23 PM, Lawrence Velázquez  wrote:

>> I would also encourage somebody to look into the need for both Xcode and 
>> Command Line Tools since Xcode 7. Apple makes it quite clear on the download 
>> page that Xcode now contains the CLTs, so installing both might well cause 
>> issues and clearly waste valuable space.
> 
> Some stubborn build systems look for stuff in /usr/include and similar 
> locations and complain if they don't exist. If anything, working on the 
> inverse configuration (CLT only, no Xcode) would be a better use of time.

Thanks for clearing that up (hard coding, that is) and I agree with you that 
CLT only is a better use of time. I have been operating that way for the last 
couple of years and have yet to run into a port that I need which actually 
required Xcode, but maybe I’ve just been lucky. I see that 
https://trac.macports.org/ticket/29172 has been there for five years now, so I 
won’t hold my breath until it happens.

-Al-
-- 
Al Varnell
Mountain View, CA






smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: MacPorts missing links

2016-09-12 Thread Sinan Karasu
I get the same thing. I have only 3 or 4 ports. So I’ll blow it away and start 
from scratch tomorrow to see what happens.

pirlouit:~ sinan$ port provides /opt/local/lib/libpng.la
/opt/local/lib/libpng.la is provided by: libpng
pirlouit:~ sinan$ 



> On Sep 12, 2016, at 7:19 PM, Ryan Schmidt  wrote:
> 
> 
>> On Sep 12, 2016, at 9:08 PM, Brandon Allbery  wrote:
>> 
>> On Mon, Sep 12, 2016 at 9:59 PM, Ryan Schmidt  
>> wrote:
>> What do you get when you run:
>> port provides /opt/local/lib/libpng.la
>> 
>> They actually provided that earlier:
>> 
>>> /opt/local/lib/libpng.la  is provided by: libpng
> 
> David provided this information about his installation but Sinan didn't yet.
> 
> But you know, not only should /opt/local/lib/libpng.la not exist on Mavericks 
> or later, it shouldn't be a symlink on any system; it should be a text file.
> 
> If it's a symlink on your system, what's it a symlink to?
> 

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


Re: MacPorts missing links

2016-09-12 Thread Brandon Allbery
On Mon, Sep 12, 2016 at 11:02 PM, Al Varnell  wrote:

> In all the years I've been using MacPorts I have never needed to reinstall
> the MacPorts base for a minor upgrade.


I think that's stated, although maybe not clearly enough. Needing to do
that on a minor upgrade would be a failure of Apple release engineering.

-- 
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: MacPorts missing links

2016-09-12 Thread Brandon Allbery
On Mon, Sep 12, 2016 at 10:24 PM, Dave Horsfall  wrote:

> Hmmm...  I've been following this thread, and I get:
>
> /opt/local/lib/libpng.la
>

And... just checked my 10.11 as well. Indeed:

skkukkuk «crawl*master» Z$ sudo find -L /opt/local -type l
>
> /opt/local/lib/libpng.la
>>
>  (and some others including the texlive files Dave Horsfall mentioned)

> skkukkuk «crawl*master» Z$ port provides /opt/local/lib/libpng.la
>
> /opt/local/lib/libpng.la is provided by: libpng
>
>
Sounds like the libpng Portfile is a tad buggy.

-- 
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: MacPorts missing links

2016-09-12 Thread Dave Horsfall
On Mon, 12 Sep 2016, Ryan Schmidt wrote:

> > pirlouit:~ sinan$ sudo find -L /opt/local -type l
> > /opt/local/lib/libpng.la
> > pirlouit:~ sinan$ 
> > 
> > The one you say I shouldn’t get. And that is the only one.

Hmmm...  I've been following this thread, and I get:

/opt/local/lib/libpng.la

but I also get:

/opt/local/libexec/texlive/binaries/a2ping
/opt/local/libexec/texlive/binaries/a5toa4
/opt/local/libexec/texlive/binaries/adhocfilelist

etc.

What did I break this time?

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: MacPorts missing links

2016-09-12 Thread Ryan Schmidt

> On Sep 12, 2016, at 9:08 PM, Brandon Allbery  wrote:
> 
> On Mon, Sep 12, 2016 at 9:59 PM, Ryan Schmidt  wrote:
> What do you get when you run:
> port provides /opt/local/lib/libpng.la
> 
> They actually provided that earlier:
> 
> > /opt/local/lib/libpng.la  is provided by: libpng

David provided this information about his installation but Sinan didn't yet.

But you know, not only should /opt/local/lib/libpng.la not exist on Mavericks 
or later, it shouldn't be a symlink on any system; it should be a text file.

If it's a symlink on your system, what's it a symlink to?

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


Re: MacPorts missing links

2016-09-12 Thread Ryan Schmidt

On Sep 12, 2016, at 6:25 AM, David Epstein wrote:

> When I now run
>> sudo find -L /opt/local -type l -exec port provides {} +
> 
> I get
>> /opt/local/lib/libpng.la is provided by: libpng
>> /opt/local/libexec/qt4/include/QtCLucene is provided by: qt4-mac
>> /opt/local/libexec/qt4/include/QtDesignerComponents is provided by: qt4-mac
>> /opt/local/libexec/qt4/Library/Frameworks/QtCLucene.framework/Headers is 
>> provided by: qt4-mac
> 
> With regard to your remark about libpng, isn’t it the case that the MacPorts 
> guide now indicates that it is not necessary to start from scratch when the 
> OS is upgraded? Anyway, I have not been starting from scratch on MacPorts 
> with recent OS upgrades. So libpng would perhaps have been left over from 
> previous operating systems,. I don’t see why it would have been uninstalled.

Officially, per the Migration wiki page, when you upgrade to a new version of 
macOS, you should install the latest Xcode and command line tools and reinstall 
MacPorts base. Those steps aren't optional.

Then you should uninstall and reinstall all ports. If you don't do that, 
MacPorts will consider all ports to be outdated, due to the change in macOS 
version number. You can then upgrade them by running "sudo port upgrade 
outdated". This might work, and I've used this method myself. But it's possible 
for you to run into problems with this due to undeclared dependencies. You may 
be able to avoid those problems by using trace mode ("port -t"), at the expense 
of some speed, and also at the expense of running into some other kinds of 
problems. Also, the trace mode in MacPorts 2.3.x may be insufficient; much work 
has been done to improve trace mode in trunk, which will be released as 
MacPorts 2.4, but that hasn't happened yet.

>>> I agree that some of the select group entry names we've chosen are not 
>>> optimal in the way in which they differ from the name of the port they 
>>> provide. It might be a pain to fix that at this late date.
> Presumably you have hard-wired this connection between a select group entry 
> name and some particular Apple binary. How do I find out which Apple binary?

Apple binary or MacPorts binary. One way to find out would be to actually 
select it (e.g. "sudo port select python python27-apple"), then see what binary 
/opt/local/bin/python points to. Usually "port select" makes many symlinks. In 
the case of the python select group, it's not just selecting what 
/opt/local/bin/python points to, but also a handful of other symlinks to other 
programs related to python.

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


Re: MacPorts missing links

2016-09-12 Thread Ryan Schmidt

> On Sep 12, 2016, at 10:53 AM, Sinan Karasu  wrote:
> 
> 
>> On Sep 12, 2016, at 4:25 AM, David Epstein  
>> wrote:
>> 
>>> sudo find -L /opt/local -type l
>>> For example, libpng.la should not have existed on your system, if your OS 
>>> is Mavericks or later.
> 
> Now you made me curious. My OS is Sierra, and has been for about a month. I 
> had installed MacPorts from sources. At first I couldn’t install much of 
> anything, since I always got an error on Sierra. About a week or so ago, 
> things sorted themselves out.

The Sierra GM has only been out for a few days, with the public release still a 
week away, so do expect a certain amount of problems with MacPorts on Sierra 
for the next month or two as port maintainers upgrade to Sierra, see what the 
problem are, and figure out how to solve them.


> Since then I’ve installed 3 ports(I believe).
> xfig
> ipe
> cgal
> 
> And this is the result I get:
> 
> pirlouit:~ sinan$ sudo find -L /opt/local -type l
> /opt/local/lib/libpng.la
> pirlouit:~ sinan$ 
> 
> The one you say I shouldn’t get. And that is the only one.

.la files are not installed by MacPorts, by default, for the vast majority of 
ports, as of OS X 10.9 Mavericks. The macports.conf setting that controls this 
is delete_la_files. (It is not listed in macports.conf by default because users 
probably shouldn't be overriding it.) Some ports (well, exactly three ports: 
ImageMagick, uriparser, xapian-core) override it because they require their own 
.la files for some reason. libpng does not override it so the .la file should 
not be there.

What do you get when you run:

port provides /opt/local/lib/libpng.la

I assume it will say it's not provided by a MacPorts port, in which case you 
have to ask yourself how it got there, if MacPorts didn't put it there. Did you 
run some third-party installer that put it (and probably other files) there? 
What is the file's creation date, and can you find any other files on your 
system created around the same time that might give you an idea of what it came 
with?

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


Re: MacPorts missing links

2016-09-12 Thread Lawrence Velázquez
> On Sep 12, 2016, at 7:25 AM, David Epstein  
> wrote:
> 
> When I now run
>> sudo find -L /opt/local -type l -exec port provides {} +
> 
> I get
>> /opt/local/lib/libpng.la is provided by: libpng
>> /opt/local/libexec/qt4/include/QtCLucene is provided by: qt4-mac
>> /opt/local/libexec/qt4/include/QtDesignerComponents is provided by: qt4-mac
>> /opt/local/libexec/qt4/Library/Frameworks/QtCLucene.framework/Headers is 
>> provided by: qt4-mac
> 
> With regard to your remark about libpng, isn’t it the case that the MacPorts 
> guide now indicates that it is not necessary to start from scratch when the 
> OS is upgraded? Anyway, I have not been starting from scratch on MacPorts 
> with recent OS upgrades. So libpng would perhaps have been left over from 
> previous operating systems,. I don’t see why it would have been uninstalled.

I'm not sure where the Guide says that, but it shouldn't. We do still recommend 
reinstalling after major OS upgrades.

https://trac.macports.org/wiki/Migration

> I should read more documentation on “port select”. I think that “man port” 
> does not give an adequate explanation, and I would welcome a pointer to 
> fuller documentation about “port select”.

The new documentation system has a "port-select" manpage, but I'm not sure if 
that has been released.

>>> I agree that some of the select group entry names we've chosen are not 
>>> optimal in the way in which they differ from the name of the port they 
>>> provide. It might be a pain to fix that at this late date.
> 
> Presumably you have hard-wired this connection between a select group entry 
> name and some particular Apple binary. How do I find out which Apple binary?

They're not really hardcoded. It's just that they've been out there for a 
while, and presumably people are using them.

The symlinks to be created are described in a *_select port's "base" file.
https://trac.macports.org/browser/trunk/dports/sysutils/python_select/files/base

The *_select port itself can create select entries corresponding to the 
system-provided installations.
https://trac.macports.org/browser/trunk/dports/sysutils/python_select/Portfile

The paths to the system files are described in separate files.
https://trac.macports.org/browser/trunk/dports/sysutils/python_select/files

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


Re: MacPorts missing links

2016-09-12 Thread Lawrence Velázquez
> On Sep 11, 2016, at 7:59 PM, David Epstein  
> wrote:
> 
> In view of all my moans and groans, I would like to make it clear that I 
> think MacPorts is great, and it adds greatly to my productivity. I use it all 
> the time, and tend to regard it as “Just there and working perfectly” usually 
> without thinking of the arduous contributions being made behind the scenes. I 
> guess one only becomes aware of this when something isn’t quite right. This 
> is rare with MacPorts, which means that it is even easier to take for granted.

No worries at all. We certainly appreciate hearing about functionality that you 
find confusing or difficult to use; it helps us decide what to work on.

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


Re: MacPorts missing links

2016-09-12 Thread Sinan Karasu

> On Sep 12, 2016, at 4:25 AM, David Epstein  
> wrote:
> 
>> sudo find -L /opt/local -type l
>> For example, libpng.la  should not have existed on your 
>> system, if your OS is Mavericks or later.

Now you made me curious. My OS is Sierra, and has been for about a month. I had 
installed MacPorts from sources. At first I couldn’t install much of anything, 
since I always got an error on Sierra. About a week or so ago, things sorted 
themselves out.

Since then I’ve installed 3 ports(I believe).
xfig
ipe
cgal

And this is the result I get:

pirlouit:~ sinan$ sudo find -L /opt/local -type l
/opt/local/lib/libpng.la
pirlouit:~ sinan$ 

The one you say I shouldn’t get. And that is the only one.

Thanks.

Sinan Karasu
Seattle WA.

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


Re: MacPorts missing links

2016-09-11 Thread David Epstein
In view of all my moans and groans, I would like to make it clear that I think 
MacPorts is great, and it adds greatly to my productivity. I use it all the 
time, and tend to regard it as “Just there and working perfectly” usually 
without thinking of the arduous contributions being made behind the scenes. I 
guess one only becomes aware of this when something isn’t quite right. This is 
rare with MacPorts, which means that it is even easier to take for granted.

I really appreciate all the work that the designers and maintainers of the 
system do, and thank you for your labours.

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


Re: MacPorts missing links

2016-09-11 Thread David Epstein
> On 11 Sep 2016, at 23:22, Ryan Schmidt  wrote:
> 
> On my system I see the contents of that directory are provided by the 
> following ports:
> 
> $ port provides /opt/local/etc/select/python3/*
> /opt/local/etc/select/python3/base is provided by: python3_select
> /opt/local/etc/select/python3/none is provided by: python3_select
> /opt/local/etc/select/python3/python33 is provided by: python33
> /opt/local/etc/select/python3/python34 is provided by: python34
> /opt/local/etc/select/python3/python35 is provided by: python35
> 
> What do you get if you run that "port provides" command?

I get
% port provides /opt/local/etc/select/python3/*
/opt/local/etc/select/python3/current is not provided by a MacPorts port.]

>> A final point, that I hope is not out-of-place. On my system
>>> port select —list llvm
>> 
>> responds with
>>> Available versions for llvm:
>>> mp-llvm-3.5
>>> none (active)
>> and you have told me that “mp-llvm-3.5” is not the name of a port.
> 
> That's correct. The name of the port is llvm-3.5. The name of its llvm select 
> group entry is mp-llvm-3.5.
> 
>> I do not understand the issues involved and their ramifications, so I may be 
>> saying something stupid, but it seems to me, as a naive user, that this 
>> reveals a rather bad design fault in “port select”. An "available version" 
>> should either be “none” or the true name of an installed port. I realize 
>> that resources  to fix things are scarce, but could the ability to choose a 
>> random name at least be acknowledged as bad practice, and could a ticket be 
>> provided for work to be done so that this behaviour becomes impossible?
> 
> I think we don't consider this to be a design fault, but a feature. In other 
> words, it was not a mistake that the select group entry can differ from a 
> port; it was a deliberate decision to allow that. As has been pointed out, we 
> want to be able to select things that are part of macOS and are not provided 
> by a port.
Yes, Brandon Allbery explained this in an email prior to this one of yours. I 
hadn’t at all realized the existence of this feature, which is clearly a good 
idea.
> I agree that some of the select group entry names we've chosen are not 
> optimal in the way in which they differ from the name of the port they 
> provide. It might be a pain to fix that at this late date.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: MacPorts missing links

2016-09-11 Thread Ryan Schmidt

> On Sep 11, 2016, at 5:37 PM, Lawrence Velázquez  wrote:
> 
>> On Sep 11, 2016, at 6:33 PM, Ryan Schmidt  wrote:
>> 
>>> On Sep 11, 2016, at 5:22 PM, Ryan Schmidt  wrote:
>>> 
 On Sep 11, 2016, at 4:57 PM, David Epstein  
 wrote:
 
 I do not understand the issues involved and their ramifications, so I may 
 be saying something stupid, but it seems to me, as a naive user, that this 
 reveals a rather bad design fault in “port select”. An "available version" 
 should either be “none” or the true name of an installed port. I realize 
 that resources  to fix things are scarce, but could the ability to choose 
 a random name at least be acknowledged as bad practice, and could a ticket 
 be provided for work to be done so that this behaviour becomes impossible?
>>> 
>>> I think we don't consider this to be a design fault, but a feature. In 
>>> other words, it was not a mistake that the select group entry can differ 
>>> from a port; it was a deliberate decision to allow that. As has been 
>>> pointed out, we want to be able to select things that are part of macOS and 
>>> are not provided by a port.
>>> 
>>> I agree that some of the select group entry names we've chosen are not 
>>> optimal in the way in which they differ from the name of the port they 
>>> provide. It might be a pain to fix that at this late date.
>> 
>> Maybe we could also display the name of the port, if any, that provides each 
>> select group entry.
> 
> That's an idea, although then entries like "python27-apple" would appear to 
> come from "python_select", which would be a little weird.

Provide a way for a port to override it, so that we can fix that to say that it 
comes from macOS whatever.version.

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


Re: MacPorts missing links

2016-09-11 Thread Lawrence Velázquez
> On Sep 11, 2016, at 6:33 PM, Ryan Schmidt  wrote:
> 
>> On Sep 11, 2016, at 5:22 PM, Ryan Schmidt  wrote:
>> 
>>> On Sep 11, 2016, at 4:57 PM, David Epstein  
>>> wrote:
>>> 
>>> I do not understand the issues involved and their ramifications, so I may 
>>> be saying something stupid, but it seems to me, as a naive user, that this 
>>> reveals a rather bad design fault in “port select”. An "available version" 
>>> should either be “none” or the true name of an installed port. I realize 
>>> that resources  to fix things are scarce, but could the ability to choose a 
>>> random name at least be acknowledged as bad practice, and could a ticket be 
>>> provided for work to be done so that this behaviour becomes impossible?
>> 
>> I think we don't consider this to be a design fault, but a feature. In other 
>> words, it was not a mistake that the select group entry can differ from a 
>> port; it was a deliberate decision to allow that. As has been pointed out, 
>> we want to be able to select things that are part of macOS and are not 
>> provided by a port.
>> 
>> I agree that some of the select group entry names we've chosen are not 
>> optimal in the way in which they differ from the name of the port they 
>> provide. It might be a pain to fix that at this late date.
> 
> Maybe we could also display the name of the port, if any, that provides each 
> select group entry.

That's an idea, although then entries like "python27-apple" would appear to 
come from "python_select", which would be a little weird.

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


Re: MacPorts missing links

2016-09-11 Thread Ryan Schmidt

> On Sep 11, 2016, at 5:33 PM, Lawrence Velázquez  wrote:
> 
>> On Sep 11, 2016, at 6:29 PM, Ryan Schmidt  wrote:
>> 
>>> On Sep 11, 2016, at 5:24 PM, Brandon Allbery wrote:
 On Sun, Sep 11, 2016 at 6:22 PM, Ryan Schmidt wrote:
 
 On my system I see the contents of that directory are provided by the 
 following ports:
>>> 
>>> I think they're complaining that the directory itself should have been 
>>> cleaned up. We don't have the concept of files/directories shared between 
>>> ports, so it just doesn't get listed and therefore doesn't get cleaned up.
>> 
>> MacPorts does delete empty directories whenever a port is deactivated...
> 
> But not all the files in the etc/select tree come from ports.
> 
>   % port provides /opt/local/etc/select/**/current
>   /opt/local/etc/select/gcc/current is not provided by a MacPorts port.
>   /opt/local/etc/select/python/current is not provided by a MacPorts port.
>   /opt/local/etc/select/python2/current is not provided by a MacPorts 
> port.
>   /opt/local/etc/select/python3/current is not provided by a MacPorts 
> port.
>   /opt/local/etc/select/virtualenv/current is not provided by a MacPorts 
> port.
> 
> This is cut from the same cloth as the symlink issue: The selection mechanism 
> is implemented half in base and half in ports, and there's something of an 
> impedance mismatch.

Gotcha, so if you did not have something selected by that group, MacPorts would 
have removed the directory when the last port providing the select group was 
deactivated, but because something was selected, its "current" file prevented 
the deactivate phase from deleting the directory. So we should also fix "port 
select" to remove empty directories when removing the "current" symlink.

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


Re: MacPorts missing links

2016-09-11 Thread Lawrence Velázquez
> On Sep 11, 2016, at 5:57 PM, David Epstein  
> wrote:
> 
> I’m not sure if I am allowed to put my name on some kind of cc list for the 
> ticket, since I’m not intending to work on the problem, but only want to know 
> when it has gone away.

Feel free to Cc yourself on the ticket Mojca linked earlier.

https://trac.macports.org/ticket/47755

> Possibly I misunderstand, but your earlier emails seem to imply that you feel 
> that the only problem with “select” in MacPorts is the creation of symlinks 
> that are not deleted when uninstalling. However, I do not believe this is the 
> whole story. For example, my command
>> port installed ‘*python*3*’
> 
> was answered
>> “None of the specified ports is installed”.
> 
> Nevertheless the directory /opt/local/etc/select/python3 remains on my system 
> as useless clutter and there is no obvious way to delete it except manually, 
> which ought to be a “No-no". This has nothing to do with symlinks.

This is not really an issue, unless you're a neat freak. The same thing happens 
with configuration files that are installed in post-activate phases.

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


Re: MacPorts missing links

2016-09-11 Thread Ryan Schmidt

> On Sep 11, 2016, at 5:22 PM, Ryan Schmidt  wrote:
> 
> 
>> On Sep 11, 2016, at 4:57 PM, David Epstein  
>> wrote:
>> 
>> Thanks very much for all your work on my issue: much appreciated.
>> 
>> However, it’s looking like too much manual work, and also somewhat 
>> hazardous, at least to me as a non-expert. Moreover, I have no confidence 
>> that everything will be consistent, even if I successfully and correctly 
>> manually delete a number of symlinks, regular files and directories from 
>> /opt/local. Rather than spend more time on the problem, I will now move 
>> /opt/local to /opt/local.old and start again from scratch.
> 
> If you like, but that sounds like a lot of work to me. It didn't sound like 
> there was anything particularly wrong with your old MacPorts installation, 
> aside from a few broken symlinks created by port select, and maybe one or two 
> other broken symlinks whose origins I'm not sure of yet. For example, 
> libpng.la should not have existed on your system, if your OS is Mavericks or 
> later.
> 
> 
>> It will be nice to have a clean installation that I don’t need to work on. 
>> I'm hoping that everything I need will install without error messages, but 
>> maybe that is overoptimistic.
>> 
>> I will avoid using “port select”  on my new installation, until I get the 
>> go-ahead that the problems have been researched and sorted. I’m not sure if 
>> I am allowed to put my name on some kind of cc list for the ticket, since 
>> I’m not intending to work on the problem, but only want to know when it has 
>> gone away.
> 
> There's no need to avoid using "port select", if you want the functionality 
> it provides. It just doesn't automatically remove its symlinks if you later 
> uninstall the port you had asked "port select" to select. Until we fix that, 
> remember to "port select GROUP none", where GROUP is the name of the select 
> group.

And certainly you can Cc yourself on any tickets you're interested in 
following, by clicking the ticket's CcMe! button.



>> I do not understand the issues involved and their ramifications, so I may be 
>> saying something stupid, but it seems to me, as a naive user, that this 
>> reveals a rather bad design fault in “port select”. An "available version" 
>> should either be “none” or the true name of an installed port. I realize 
>> that resources  to fix things are scarce, but could the ability to choose a 
>> random name at least be acknowledged as bad practice, and could a ticket be 
>> provided for work to be done so that this behaviour becomes impossible?
> 
> I think we don't consider this to be a design fault, but a feature. In other 
> words, it was not a mistake that the select group entry can differ from a 
> port; it was a deliberate decision to allow that. As has been pointed out, we 
> want to be able to select things that are part of macOS and are not provided 
> by a port.
> 
> I agree that some of the select group entry names we've chosen are not 
> optimal in the way in which they differ from the name of the port they 
> provide. It might be a pain to fix that at this late date.

Maybe we could also display the name of the port, if any, that provides each 
select group entry.

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


Re: MacPorts missing links

2016-09-11 Thread Lawrence Velázquez
> On Sep 11, 2016, at 6:29 PM, Ryan Schmidt  wrote:
> 
>> On Sep 11, 2016, at 5:24 PM, Brandon Allbery wrote:
>>> On Sun, Sep 11, 2016 at 6:22 PM, Ryan Schmidt wrote:
>>> 
>>> On my system I see the contents of that directory are provided by the 
>>> following ports:
>> 
>> I think they're complaining that the directory itself should have been 
>> cleaned up. We don't have the concept of files/directories shared between 
>> ports, so it just doesn't get listed and therefore doesn't get cleaned up.
> 
> MacPorts does delete empty directories whenever a port is deactivated...

But not all the files in the etc/select tree come from ports.

% port provides /opt/local/etc/select/**/current
/opt/local/etc/select/gcc/current is not provided by a MacPorts port.
/opt/local/etc/select/python/current is not provided by a MacPorts port.
/opt/local/etc/select/python2/current is not provided by a MacPorts 
port.
/opt/local/etc/select/python3/current is not provided by a MacPorts 
port.
/opt/local/etc/select/virtualenv/current is not provided by a MacPorts 
port.

This is cut from the same cloth as the symlink issue: The selection mechanism 
is implemented half in base and half in ports, and there's something of an 
impedance mismatch.

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


Re: MacPorts missing links

2016-09-11 Thread Ryan Schmidt

On Sep 11, 2016, at 5:24 PM, Brandon Allbery wrote:
> On Sun, Sep 11, 2016 at 6:22 PM, Ryan Schmidt wrote:
>> On my system I see the contents of that directory are provided by the 
>> following ports:
> 
> I think they're complaining that the directory itself should have been 
> cleaned up. We don't have the concept of files/directories shared between 
> ports, so it just doesn't get listed and therefore doesn't get cleaned up.

MacPorts does delete empty directories whenever a port is deactivated...


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


Re: MacPorts missing links

2016-09-11 Thread Brandon Allbery
On Sun, Sep 11, 2016 at 6:22 PM, Ryan Schmidt 
wrote:

> On my system I see the contents of that directory are provided by the
> following ports:


I think they're complaining that the directory itself should have been
cleaned up. We don't have the concept of files/directories shared between
ports, so it just doesn't get listed and therefore doesn't get cleaned up.

-- 
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: MacPorts missing links

2016-09-11 Thread Ryan Schmidt

> On Sep 11, 2016, at 4:57 PM, David Epstein  
> wrote:
> 
> Thanks very much for all your work on my issue: much appreciated.
> 
> However, it’s looking like too much manual work, and also somewhat hazardous, 
> at least to me as a non-expert. Moreover, I have no confidence that 
> everything will be consistent, even if I successfully and correctly manually 
> delete a number of symlinks, regular files and directories from /opt/local. 
> Rather than spend more time on the problem, I will now move /opt/local to 
> /opt/local.old and start again from scratch.

If you like, but that sounds like a lot of work to me. It didn't sound like 
there was anything particularly wrong with your old MacPorts installation, 
aside from a few broken symlinks created by port select, and maybe one or two 
other broken symlinks whose origins I'm not sure of yet. For example, libpng.la 
should not have existed on your system, if your OS is Mavericks or later.


> It will be nice to have a clean installation that I don’t need to work on. 
> I'm hoping that everything I need will install without error messages, but 
> maybe that is overoptimistic.
> 
> I will avoid using “port select”  on my new installation, until I get the 
> go-ahead that the problems have been researched and sorted. I’m not sure if I 
> am allowed to put my name on some kind of cc list for the ticket, since I’m 
> not intending to work on the problem, but only want to know when it has gone 
> away.

There's no need to avoid using "port select", if you want the functionality it 
provides. It just doesn't automatically remove its symlinks if you later 
uninstall the port you had asked "port select" to select. Until we fix that, 
remember to "port select GROUP none", where GROUP is the name of the select 
group.

> Possibly I misunderstand, but your earlier emails seem to imply that you feel 
> that the only problem with “select” in MacPorts is the creation of symlinks 
> that are not deleted when uninstalling.

I would concur with that.

> However, I do not believe this is the whole story. For example, my command
>> port installed ‘*python*3*’
> 
> was answered
>> “None of the specified ports is installed”.
> 
> Nevertheless the directory /opt/local/etc/select/python3 remains on my system 
> as useless clutter and there is no obvious way to delete it except manually, 
> which ought to be a “No-no". This has nothing to do with symlinks.

On my system I see the contents of that directory are provided by the following 
ports:

$ port provides /opt/local/etc/select/python3/*
/opt/local/etc/select/python3/base is provided by: python3_select
/opt/local/etc/select/python3/none is provided by: python3_select
/opt/local/etc/select/python3/python33 is provided by: python33
/opt/local/etc/select/python3/python34 is provided by: python34
/opt/local/etc/select/python3/python35 is provided by: python35

What do you get if you run that "port provides" command?


> A final point, that I hope is not out-of-place. On my system
>> port select —list llvm
> 
> responds with
>> Available versions for llvm:
>>  mp-llvm-3.5
>>  none (active)
> and you have told me that “mp-llvm-3.5” is not the name of a port.

That's correct. The name of the port is llvm-3.5. The name of its llvm select 
group entry is mp-llvm-3.5.

> I do not understand the issues involved and their ramifications, so I may be 
> saying something stupid, but it seems to me, as a naive user, that this 
> reveals a rather bad design fault in “port select”. An "available version" 
> should either be “none” or the true name of an installed port. I realize that 
> resources  to fix things are scarce, but could the ability to choose a random 
> name at least be acknowledged as bad practice, and could a ticket be provided 
> for work to be done so that this behaviour becomes impossible?

I think we don't consider this to be a design fault, but a feature. In other 
words, it was not a mistake that the select group entry can differ from a port; 
it was a deliberate decision to allow that. As has been pointed out, we want to 
be able to select things that are part of macOS and are not provided by a port.

I agree that some of the select group entry names we've chosen are not optimal 
in the way in which they differ from the name of the port they provide. It 
might be a pain to fix that at this late date.





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


Re: MacPorts missing links

2016-09-11 Thread Brandon Allbery
On Sun, Sep 11, 2016 at 5:57 PM, David Epstein 
wrote:

> and you have told me that “mp-llvm-3.5” is not the name of a port. I do
> not understand the issues involved and their ramifications, so I may be
> saying something stupid, but it seems to me, as a naive user, that this
> reveals a rather bad design fault in “port select”.


So do we have to also install Apple's version of Python as a port in
addition to (or, perhaps, on top of? speaking of absolute no-nos) so that
selecting one of Apple's preinstalled Pythons is permissible?

-- 
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: MacPorts missing links

2016-09-11 Thread David Epstein
Thanks very much for all your work on my issue: much appreciated.

However, it’s looking like too much manual work, and also somewhat hazardous, 
at least to me as a non-expert. Moreover, I have no confidence that everything 
will be consistent, even if I successfully and correctly manually delete a 
number of symlinks, regular files and directories from /opt/local. Rather than 
spend more time on the problem, I will now move /opt/local to /opt/local.old 
and start again from scratch. It will be nice to have a clean installation that 
I don’t need to work on. I'm hoping that everything I need will install without 
error messages, but maybe that is overoptimistic.

I will avoid using “port select”  on my new installation, until I get the 
go-ahead that the problems have been researched and sorted. I’m not sure if I 
am allowed to put my name on some kind of cc list for the ticket, since I’m not 
intending to work on the problem, but only want to know when it has gone away.

Possibly I misunderstand, but your earlier emails seem to imply that you feel 
that the only problem with “select” in MacPorts is the creation of symlinks 
that are not deleted when uninstalling. However, I do not believe this is the 
whole story. For example, my command
> port installed ‘*python*3*’

was answered
> “None of the specified ports is installed”.

Nevertheless the directory /opt/local/etc/select/python3 remains on my system 
as useless clutter and there is no obvious way to delete it except manually, 
which ought to be a “No-no". This has nothing to do with symlinks.

A final point, that I hope is not out-of-place. On my system
> port select —list llvm

responds with
> Available versions for llvm:
>   mp-llvm-3.5
>   none (active)
and you have told me that “mp-llvm-3.5” is not the name of a port. I do not 
understand the issues involved and their ramifications, so I may be saying 
something stupid, but it seems to me, as a naive user, that this reveals a 
rather bad design fault in “port select”. An "available version" should either 
be “none” or the true name of an installed port. I realize that resources  to 
fix things are scarce, but could the ability to choose a random name at least 
be acknowledged as bad practice, and could a ticket be provided for work to be 
done so that this behaviour becomes impossible?
Best wishes
David
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: MacPorts missing links

2016-09-11 Thread Lawrence Velázquez
> On Sep 11, 2016, at 2:41 AM, David Epstein  
> wrote:
> 
> I ran the suggested find command and double checked that all the entries are 
> broken symlinks. Ideally I would like to get rid of all of them, but safely. 
> From my point of view, the danger is that these filenames occur in some 
> different list in /opt/local, unknown to me, and that this list would be 
> corrupted if I simply delete the broken symlinks using /bin/rm .

I don't think "port select" registers its links anywhere.

These files are created by the python select group. You ought to be able to 
delete them.

> /opt/local/bin/2to3
> /opt/local/bin/idle
> /opt/local/bin/pydoc
> /opt/local/bin/python
> /opt/local/bin/python-config
> /opt/local/bin/pythonw
> /opt/local/bin/smtpd.py
> /opt/local/etc/select/python/current
> /opt/local/man/man1/python.1
> /opt/local/share/man/man1/python.1
> /opt/local/Library/Frameworks/Python.framework/Headers
> /opt/local/Library/Frameworks/Python.framework/Python
> /opt/local/Library/Frameworks/Python.framework/Resources
> /opt/local/Library/Frameworks/Python.framework/Versions/Current

python3:

> /opt/local/bin/2to3-3
> /opt/local/bin/idle3
> /opt/local/bin/pydoc3
> /opt/local/bin/python3
> /opt/local/bin/python3-config
> /opt/local/bin/python3m
> /opt/local/bin/python3m-config
> /opt/local/bin/pyvenv
> /opt/local/etc/select/python3/current
> /opt/local/man/man1/python3.1
> /opt/local/share/man/man1/python3.1

ipython:

> /opt/local/bin/iptest
> /opt/local/bin/ipython
> /opt/local/etc/select/ipython/current
> /opt/local/share/man/man1/ipython.1

ipython2:

> /opt/local/bin/iptest2
> /opt/local/bin/ipython2
> /opt/local/etc/select/ipython2/current
> /opt/local/share/man/man1/ipython2.1

pip:

> /opt/local/bin/pip
> /opt/local/etc/select/pip/current

I initially thought that these were created by ipython and ipython2, but their 
base files seem to disagree, so I don't know where these are from.

> /opt/local/man/man1/ipython.1
> /opt/local/man/man1/ipython2.1


I assume these are parts of "libpng" and "qt4-mac" or "qt4-x11". See what this 
tells you:

find -L /opt/local -type l -exec port provides {} +

> /opt/local/lib/libpng.la
> /opt/local/libexec/qt4/include/QtCLucene
> /opt/local/libexec/qt4/include/QtDesignerComponents
> /opt/local/libexec/qt4/Library/Frameworks/QtCLucene.framework/Headers

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


Re: MacPorts missing links

2016-09-11 Thread David Epstein
On 11 Sep 2016, at 14:41, Lawrence Velázquez  wrote:
> 
>> On Sep 11, 2016, at 4:13 AM, David Epstein  
>> wrote:
>> 
>> For those few interested in this thread, and who have not followed so far, 
>> the relevant line of output from
>> “port select —summary” was
>>> llvm   none  mp-llvm-3.5 none
>> 
>> I think that this is a either a bug in “port select —summary” or a 
>> misinterpretation of the output from
>> “port select —summary”.
>> 
>> In contrast, here is what “port installed” thinks:
>>> port installed mp-livm-3.5
>> gives
>>> None of the specified ports are installed.
> 
> Port names and select entries need not match. The "mp-llvm-3.5" select entry 
> corresponds to the "llvm-3.5" port.
> 
> vq

Thanks for clearing up my misconception/misinterpretation of the output from 
“port select —summary”.
Is there a port command that would have given me this information?

David

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


Re: MacPorts missing links

2016-09-11 Thread David Epstein
livm was my error due to poor eyesight. It should have been llvm all the time.

> On 11 Sep 2016, at 14:55, Sinan Karasu  wrote:
> 
> I don’t get the correspondence between “llvm” and “livm” in your posts. Is it 
> a typo, or are there really two different ports?
> 
>> On Sep 11, 2016, at 1:13 AM, David Epstein  
>> wrote:
>> 
>>> livm
> 

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


Re: MacPorts missing links

2016-09-11 Thread Sinan Karasu
I don’t get the correspondence between “llvm” and “livm” in your posts. Is it a 
typo, or are there really two different ports?

> On Sep 11, 2016, at 1:13 AM, David Epstein  
> wrote:
> 
>> livm

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


Re: MacPorts missing links

2016-09-11 Thread Lawrence Velázquez
> On Sep 11, 2016, at 6:24 AM, David Epstein  
> wrote:
> 
> I hope that I’m believed when I say that I’m extremely careful never to 
> operate on /opt/local except via port. I do use programs like unix find and 
> unix ls that are not supposed to change anything.

No, it's very clear that you haven't been mucking around inside your MacPorts 
prefix. The issue is that select symlinks are not updated when the selected 
port is deactivated. That is not great behavior.

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


Re: MacPorts missing links

2016-09-11 Thread Lawrence Velázquez
> On Sep 11, 2016, at 4:13 AM, David Epstein  
> wrote:
> 
> For those few interested in this thread, and who have not followed so far, 
> the relevant line of output from
> “port select —summary” was
>> llvm   none  mp-llvm-3.5 none
> 
> I think that this is a either a bug in “port select —summary” or a 
> misinterpretation of the output from
> “port select —summary”.
> 
> In contrast, here is what “port installed” thinks:
>> port installed mp-livm-3.5
> gives
>> None of the specified ports are installed.

Port names and select entries need not match. The "mp-llvm-3.5" select entry 
corresponds to the "llvm-3.5" port.

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


Re: MacPorts missing links

2016-09-11 Thread Lawrence Velázquez
> On Sep 11, 2016, at 3:40 AM, David Epstein  
> wrote:
> 
>> On 10 Sep 2016, at 23:10, Lawrence Velázquez  wrote:
> 
> … snip …
> 
 Did you uninstall python27?
>>> 
>>> I think so. The ls -l command above does not find /opt/local/bin/python*, 
>>> except for symbolic links.
>>> What port command could I give to make sure?
>> 
>> "port installed python27 and active”
> 
> Confusingly this gets an answer that is readily misinterpreted, namely
>> None of the specified ports are installed.
> 
> In contrast
>> port installed python27
> 
> does not (inadvertently) deceive: it gives
>> The following ports are currently installed:
>>  python27 @2.7.11_2

Yes, that's right. That port *is not active*, so it was not displayed by the 
first command.

>> What you could try is  explicitly setting and then unsetting:
>> 
>>  sudo port select --set python python27-apple
> 
> I tried this and got:
>> Selecting 'python27-apple' for 'python' failed: symlink: 
>> /opt/local/etc/select/python/current -> python27-apple: file already exists
> So then I did
>> ls -l /opt/local/etc/select/python/current
> and got
>> lrwxr-xr-x  1 root  admin  8  9 Jun 19:13 
>> /opt/local/etc/select/python/current@ -> python27
> This seems to me to indicate a bug in “port select —summary”.

No, the bug is in the way base doesn't clean up select links when the selected 
port is deactivated.

> Firstly, it seems to answer incorrectly for inactive ports, like python27 in 
> my case. I would have expected “port select —summary” to give python27 as an 
> option.

Why? You can't select an inactive port.

> Secondly, it seems to incorrectly and indirectly imply that python26-apple 
> and python27-apple are installed, which I think was your interpretation, but 
> they aren’t installed, as I have checked with the “port installed” command.

The "python*-apple" entries denote the system Python installations. There are 
no ports with those names.

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


Re: MacPorts missing links

2016-09-11 Thread Craig Treleaven
> On Sep 11, 2016, at 3:40 AM, David Epstein  
> wrote:
> 
>> On 10 Sep 2016, at 23:10, Lawrence Velázquez  wrote:
> 
> … snip …
> 
 Did you uninstall python27?
>>> 
>>> I think so. The ls -l command above does not find /opt/local/bin/python*, 
>>> except for symbolic links.
>>> What port command could I give to make sure?
>> 
>> "port installed python27 and active”
> 
> Confusingly this gets an answer that is readily misinterpreted, namely
>> None of the specified ports are installed.
> 
> In contrast
>> port installed python27
> 
> does not (inadvertently) deceive: it gives
>> The following ports are currently installed:
>>  python27 @2.7.11_2
> 

Sorry, I haven’t followed the whole thread but the part about ‘port installed’ 
caught my eye.  On my system:

$ port installed python27
The following ports are currently installed:
  python27 @2.7.10_2
  python27 @2.7.10_3
  python27 @2.7.11_0
  python27 @2.7.12_1 (active)

I have four versions of python27 installed but (sensibly) only one is active.  
I interpret the output from your system to mean that you had python27 installed 
and active but now it is not active.  Probably because of a command like ‘sudo 
port deactivate python27 @2.7.12_1’.

You should be able to get your python back with ‘sudo port activate python27 
@2.7.11_2’.

HTH

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


Re: MacPorts missing links

2016-09-11 Thread David Epstein
I hope that I’m believed when I say that I’m extremely careful never to operate 
on /opt/local except via port. I do use programs like unix find and unix ls 
that are not supposed to change anything.

Trying to demistify the line from the output of “port select —summary” 
> llvm   none  mp-llvm-3.5 none
I did the following
> sudo find /opt/local/ -type f -exec egrep -l llvm {} \; -print | egrep select 
> | tee llvm

and found the following files

> /opt/local//etc/select/llvm/base
> /opt/local//etc/select/llvm/mp-llvm-3.5
> /opt/local//var/macports/registry/portfiles/gcc_select-0.1_8/402c19e245d305006c81d326c0b60409d53996d6b33cd8b23ff9e19d473410ff-1587/Portfile
> /opt/local//var/macports/registry/portfiles/llvm_select-1.0_0/d46f373920a0c44fe0fa99cfec9bd161b316451d185d5ac62ed2a86da86a748e-733/Portfile
> /opt/local//var/macports/registry/portfiles/llvm_select-2_0/1843b74f59af89e60f61d519191491ca9a751228d95f1379b167336de9b6ba4e-731/Portfile
> /opt/local//var/macports/sources/rsync.macports.org/release/ports/multimedia/HandBrake/files/0011-MP-libav-Respect-our-compiler-selection-on-Darwin-i3.patch
> /opt/local//var/macports/sources/rsync.macports.org/release/ports/sysutils/gcc_select/files/llvm-gcc42
> /opt/local//var/macports/sources/rsync.macports.org/release/ports/sysutils/gcc_select/Portfile
> /opt/local//var/macports/sources/rsync.macports.org/release/ports/sysutils/llvm_select/files/base
> /opt/local//var/macports/sources/rsync.macports.org/release/ports/sysutils/llvm_select/Portfile

Whether that would help debug the erroneous behaviour of “port select —summary” 
or not, I leave in the hands of more knowledgeable and competent MacPorters.

I can either live with this lack of consistency in my /opt/local files or I can 
erase /opt/local and start again, or maybe there is a third choice. I would 
welcome advice from the list.

Best wishes
David Epstein


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


Re: MacPorts missing links

2016-09-11 Thread David Epstein

> On 10 Sep 2016, at 23:05, Brandon Allbery  wrote:

…snip...
> "port select --summary" reports as "none" in that case because the file 
> describing the previously selected option was removed and therefore is not a 
> valid setting. More to the point, if the options do not include a 
> MacPorts-installed one, then you can safely assume you do not have any 
> related port installed. For reference, your summary reports only one setting 
> for which a MacPorts port is installed: llvm 3.5 (mp-llvm-3.5) for llvm.

For those few interested in this thread, and who have not followed so far, the 
relevant line of output from
“port select —summary” was
> llvm   none  mp-llvm-3.5 none

I think that this is a either a bug in “port select —summary” or a 
misinterpretation of the output from
“port select —summary”.

In contrast, here is what “port installed” thinks:
> port installed mp-livm-3.5
gives
> None of the specified ports are installed.

I checked with unix:
> sudo find /opt/local -name "*livm*" -print
gave a null response, so this isn’t even a broken symlink

If I was more confident, I would submit a bug report. If someone else feels 
like doing this, I can cooperate by running other commands on my system and 
reporting the results to the “someone else”.

David Epstein


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


Re: MacPorts missing links

2016-09-11 Thread David Epstein
> On 10 Sep 2016, at 23:10, Lawrence Velázquez  wrote:

… snip …

>>> Did you uninstall python27?
>> 
>> I think so. The ls -l command above does not find /opt/local/bin/python*, 
>> except for symbolic links.
>> What port command could I give to make sure?
> 
> "port installed python27 and active”

Confusingly this gets an answer that is readily misinterpreted, namely
> None of the specified ports are installed.

In contrast
> port installed python27

does not (inadvertently) deceive: it gives
> The following ports are currently installed:
>   python27 @2.7.11_2

…snip…

>> I ran “port select —summary” as you suggested and got the response
>> 
>> Name   Selected  Options
>>      ===
>> cython none  none
>> gccnone  none
>> ipythonnone  none
>> ipython2   none  none
>> ipython3   none  none
>> llvm   none  mp-llvm-3.5 none
>> nosetests  none  none
>> pipnone  none
>> python none  python26-apple python27-apple none
>> python2none  python26-apple python27-apple none
>> python3none  none

…snip…

>  What you could try is  explicitly setting and then unsetting:
> 
>   sudo port select --set python python27-apple

I tried this and got:
> Selecting 'python27-apple' for 'python' failed: symlink: 
> /opt/local/etc/select/python/current -> python27-apple: file already exists
So then I did
> ls -l /opt/local/etc/select/python/current
and got
> lrwxr-xr-x  1 root  admin  8  9 Jun 19:13 
> /opt/local/etc/select/python/current@ -> python27
This seems to me to indicate a bug in “port select —summary”. Firstly, it seems 
to answer incorrectly for inactive ports, like python27 in my case. I would 
have expected “port select —summary” to give python27 as an option. Secondly, 
it seems to incorrectly and indirectly imply that python26-apple and 
python27-apple are installed, which I think was your interpretation, but they 
aren’t installed, as I have checked with the “port installed” command.

It does feel as though I will, with the help of the list, be able to clean up 
my ports: I had been thinking that I would have to delete everything in 
/opt/local and start again.

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


Re: MacPorts missing links

2016-09-11 Thread David Epstein
> On 10 Sep 2016, at 23:13, Lawrence Velázquez  wrote:
> 

… snip …

> Run this:
> 
>   find -L /opt/local -type l
> 
> This will print any broken symlinks in your MacPorts prefix. Email the output 
> to this list, and we can tell you what you can safely delete.
> 
> vq

I ran the suggested find command and double checked that all the entries are 
broken symlinks. Ideally I would like to get rid of all of them, but safely. 
From my point of view, the danger is that these filenames occur in some 
different list in /opt/local, unknown to me, and that this list would be 
corrupted if I simply delete the broken symlinks using /bin/rm .

/opt/local/bin/2to3
/opt/local/bin/2to3-3
/opt/local/bin/idle
/opt/local/bin/idle3
/opt/local/bin/iptest
/opt/local/bin/iptest2
/opt/local/bin/ipython
/opt/local/bin/ipython2
/opt/local/bin/pip
/opt/local/bin/pydoc
/opt/local/bin/pydoc3
/opt/local/bin/python
/opt/local/bin/python-config
/opt/local/bin/python3
/opt/local/bin/python3-config
/opt/local/bin/python3m
/opt/local/bin/python3m-config
/opt/local/bin/pythonw
/opt/local/bin/pyvenv
/opt/local/bin/smtpd.py
/opt/local/etc/select/ipython/current
/opt/local/etc/select/ipython2/current
/opt/local/etc/select/pip/current
/opt/local/etc/select/python/current
/opt/local/etc/select/python3/current
/opt/local/lib/libpng.la
/opt/local/libexec/qt4/include/QtCLucene
/opt/local/libexec/qt4/include/QtDesignerComponents
/opt/local/libexec/qt4/Library/Frameworks/QtCLucene.framework/Headers
/opt/local/Library/Frameworks/Python.framework/Headers
/opt/local/Library/Frameworks/Python.framework/Python
/opt/local/Library/Frameworks/Python.framework/Resources
/opt/local/Library/Frameworks/Python.framework/Versions/Current
/opt/local/man/man1/ipython.1
/opt/local/man/man1/ipython2.1
/opt/local/man/man1/python.1
/opt/local/man/man1/python3.1
/opt/local/share/man/man1/ipython.1
/opt/local/share/man/man1/ipython2.1
/opt/local/share/man/man1/python.1
/opt/local/share/man/man1/python3.1


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


Re: MacPorts missing links

2016-09-10 Thread Lawrence Velázquez
> On Sep 10, 2016, at 5:51 PM, David Epstein  
> wrote:
> 
> I do not want to rely on my memory of which of these I have uninstalled. I 
> need to be told by a reliable program.

Run this:

find -L /opt/local -type l

This will print any broken symlinks in your MacPorts prefix. Email the output 
to this list, and we can tell you what you can safely delete.

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


Re: MacPorts missing links

2016-09-10 Thread Lawrence Velázquez
> On Sep 10, 2016, at 5:51 PM, David Epstein  
> wrote:
> 
>> On 10 Sep 2016, at 19:38, Lawrence Velázquez  wrote:
>> 
>> Did you uninstall python27?
> 
> I think so. The ls -l command above does not find /opt/local/bin/python*, 
> except for symbolic links.
> What port command could I give to make sure?

"port installed python27 and active"

> What port command can I give to extirpate remnants of an uninstalled port, if 
> there are any remnants?

There isn't one, to my knowledge. By definition, uninstalling a port removes 
its archive, which is how we could tell what files it installed.

IIRC the only "remnants" might be files created by a post-activate phase, which 
MacPorts does not track. Deactivation should remove everything else.

Your issue is not related to any of this, though.

> I ran “port select —summary” as you suggested and got the response
> 
> Name   Selected  Options
>      ===
> cython none  none
> gccnone  none
> ipythonnone  none
> ipython2   none  none
> ipython3   none  none
> llvm   none  mp-llvm-3.5 none
> nosetests  none  none
> pipnone  none
> python none  python26-apple python27-apple none
> python2none  python26-apple python27-apple none
> python3none  none

Okay, I was thinking that the groups would still have the stale setting, but 
they don't, so this won't help.

> I do not want to rely on my memory of which of these I have uninstalled. I 
> need to be told by a reliable program. What would happen if I gave one of 
> your commands below, with argument a port that was still installed?

Nothing will happen, I think, because the groups are already set to "none". 
What you could try is  explicitly setting and then unsetting:

sudo port select --set python python27-apple
sudo port select --set python none

And likewise for "python2". Unfortunately you don't have any Python 3 ports 
installed.

> My guess is that only the symbolic link would be removed, leaving the true 
> file in place, but I would like to be sure before I take any action.

Correct; "port select" does not affect the contents of any ports.

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


Re: MacPorts missing links

2016-09-10 Thread Brandon Allbery
On Sat, Sep 10, 2016 at 5:51 PM, David Epstein 
wrote:

> What would happen if I gave one of your commands below, with argument a
> port that was still installed?


"port select --summary" reports as "none" in that case because the file
describing the previously selected option was removed and therefore is not
a valid setting. More to the point, if the options do not include a
MacPorts-installed one, then you can safely assume you do not have any
related port installed. For reference, your summary reports only one
setting for which a MacPorts port is installed: llvm 3.5 (mp-llvm-3.5) for
llvm.

"port select" cannot remove ports, nor should it affect any port builds (it
may actually do so, but this would be a bug that should be reported against
the port trying to use the `port select` symlink instead of an explicit
version). It is provided solely for user convenience, and should always be
safe with respect to both MacPorts and your system.

 What would happen if I gave one of your commands below, with argument a
> port that was still installed?


The default symlinks would be removed, if they exist. These would only
exist if you had done `port select` previously. They do not come from any
port, and no port should rely on their existence.

-- 
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: MacPorts missing links

2016-09-10 Thread David Epstein
Thanks for your help:

> On 10 Sep 2016, at 19:38, Lawrence Velázquez  wrote:
> 
>> On Sep 10, 2016, at 1:42 PM, David Epstein  
>> wrote:
>> 
>> I gave the command:
>> 
>> ls -l /opt/local/bin/py*
>> and the system replied:
>> 
>>> lrwxr-xr-x  1 root  wheel  23  9 Jun 19:13 /opt/local/bin/pydoc@ -> 
>>> /opt/local/bin/pydoc2.7
>>> lrwxr-xr-x  1 root  wheel  23  9 Jun 17:19 /opt/local/bin/pydoc3@ -> 
>>> /opt/local/bin/pydoc3.5
>>> lrwxr-xr-x  1 root  wheel  24  9 Jun 19:13 /opt/local/bin/python@ -> 
>>> /opt/local/bin/python2.7
>>> lrwxr-xr-x  1 root  wheel  31  9 Jun 19:13 /opt/local/bin/python-config@ -> 
>>> /opt/local/bin/python2.7-config
>>> lrwxr-xr-x  1 root  wheel  24  9 Jun 17:19 /opt/local/bin/python3@ -> 
>>> /opt/local/bin/python3.5
>>> lrwxr-xr-x  1 root  wheel  31  9 Jun 17:19 /opt/local/bin/python3-config@ 
>>> -> /opt/local/bin/python3.5-config
>>> lrwxr-xr-x  1 root  wheel  25  9 Jun 17:19 /opt/local/bin/python3m@ -> 
>>> /opt/local/bin/python3.5m
>>> lrwxr-xr-x  1 root  wheel  32  9 Jun 17:19 /opt/local/bin/python3m-config@ 
>>> -> /opt/local/bin/python3.5m-config
>>> lrwxr-xr-x  1 root  wheel  25  9 Jun 19:13 /opt/local/bin/pythonw@ -> 
>>> /opt/local/bin/pythonw2.7
>>> lrwxr-xr-x  1 root  wheel  25  9 Jun 17:19 /opt/local/bin/pyvenv@ -> 
>>> /opt/local/bin/pyvenv-3.5
> 
> Those are symlinks created by "port select". Presumably you set up the 
> python, python2, and python3 select groups at some point.
> 
>> You will see that none of the files on the righthand side of the arrow -> 
>> appears on any lefthand side. I tried “port provides” on both lefthand and 
>> righthand sides and received error messages from port such as
>>> /opt/local/bin/pydoc2.7 does not exist.
> 
> Did you uninstall python27?

I think so. The ls -l command above does not find /opt/local/bin/python*, 
except for symbolic links.
What port command could I give to make sure?

What port command can I give to extirpate remnants of an uninstalled port, if 
there are any remnants?

>> and
>>> /opt/local/bin/pydoc is not provided by a MacPorts port.
> 
> Right, because that file was created by "port select" and not a port.
> 
>> How do I get rid of the symbolic links, other than using /bin/rm, something 
>> I have been told never to do?
>> 
>> How can I find all hanging links like this in /opt? Presumably there is a 
>> clever formula using unix find.
> 
> Try running "port select --summary" (although I'm not sure whether this 
> feature has been released). It will list the select groups on your system and 
> their current settings. If any of those settings corresponds to a port you 
> have uninstalled, you should be able to remove the symlinks with

I ran “port select —summary” as you suggested and got the response

Name   Selected  Options
     ===
cython none  none
gccnone  none
ipythonnone  none
ipython2   none  none
ipython3   none  none
llvm   none  mp-llvm-3.5 none
nosetests  none  none
pipnone  none
python none  python26-apple python27-apple none
python2none  python26-apple python27-apple none
python3none  none

I do not want to rely on my memory of which of these I have uninstalled. I need 
to be told by a reliable program. What would happen if I gave one of your 
commands below, with argument a port that was still installed? Since I do not 
yet know the answer to that question, I will refrain for the moment from 
issuing any of these commands. My guess is that only the symbolic link would be 
removed, leaving the true file in place, but I would like to be sure before I 
take any action.

>   sudo port select --set python none
>   sudo port select --set python2 none
>   sudo port select --set python3 none
>   etc etc etc
> 
>> I wonder what causes this kind of problem? I cannot remember any of my port 
>> processes terminating incorrectly. I have lately been uninstalling 
>> python-related ports, because I had too many different versions of python on 
>> my machine, and I was getting confused.
> 
> The symlinks created by "port select" are not modified if the selected port 
> is subsequently deactivated or uninstalled. I think there is an open ticket 
> about this, but I can't find it at the moment.
> 
> vq

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


Re: MacPorts missing links

2016-09-10 Thread Mojca Miklavec
On 10 September 2016 at 20:38, Lawrence Velázquez wrote:
>
>> I wonder what causes this kind of problem? I cannot remember any of my port 
>> processes terminating incorrectly. I have lately been uninstalling 
>> python-related ports, because I had too many different versions of python on 
>> my machine, and I was getting confused.
>
> The symlinks created by "port select" are not modified if the selected port 
> is subsequently deactivated or uninstalled. I think there is an open ticket 
> about this, but I can't find it at the moment.

https://trac.macports.org/ticket/47755

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


Re: MacPorts missing links

2016-09-10 Thread Lawrence Velázquez
> On Sep 10, 2016, at 1:42 PM, David Epstein  
> wrote:
> 
> I gave the command:
> 
> ls -l /opt/local/bin/py*
> and the system replied:
> 
>> lrwxr-xr-x  1 root  wheel  23  9 Jun 19:13 /opt/local/bin/pydoc@ -> 
>> /opt/local/bin/pydoc2.7
>> lrwxr-xr-x  1 root  wheel  23  9 Jun 17:19 /opt/local/bin/pydoc3@ -> 
>> /opt/local/bin/pydoc3.5
>> lrwxr-xr-x  1 root  wheel  24  9 Jun 19:13 /opt/local/bin/python@ -> 
>> /opt/local/bin/python2.7
>> lrwxr-xr-x  1 root  wheel  31  9 Jun 19:13 /opt/local/bin/python-config@ -> 
>> /opt/local/bin/python2.7-config
>> lrwxr-xr-x  1 root  wheel  24  9 Jun 17:19 /opt/local/bin/python3@ -> 
>> /opt/local/bin/python3.5
>> lrwxr-xr-x  1 root  wheel  31  9 Jun 17:19 /opt/local/bin/python3-config@ -> 
>> /opt/local/bin/python3.5-config
>> lrwxr-xr-x  1 root  wheel  25  9 Jun 17:19 /opt/local/bin/python3m@ -> 
>> /opt/local/bin/python3.5m
>> lrwxr-xr-x  1 root  wheel  32  9 Jun 17:19 /opt/local/bin/python3m-config@ 
>> -> /opt/local/bin/python3.5m-config
>> lrwxr-xr-x  1 root  wheel  25  9 Jun 19:13 /opt/local/bin/pythonw@ -> 
>> /opt/local/bin/pythonw2.7
>> lrwxr-xr-x  1 root  wheel  25  9 Jun 17:19 /opt/local/bin/pyvenv@ -> 
>> /opt/local/bin/pyvenv-3.5

Those are symlinks created by "port select". Presumably you set up the python, 
python2, and python3 select groups at some point.

> You will see that none of the files on the righthand side of the arrow -> 
> appears on any lefthand side. I tried “port provides” on both lefthand and 
> righthand sides and received error messages from port such as
>> /opt/local/bin/pydoc2.7 does not exist.

Did you uninstall python27?

> and
>> /opt/local/bin/pydoc is not provided by a MacPorts port.

Right, because that file was created by "port select" and not a port.

> How do I get rid of the symbolic links, other than using /bin/rm, something I 
> have been told never to do?
> 
> How can I find all hanging links like this in /opt? Presumably there is a 
> clever formula using unix find.

Try running "port select --summary" (although I'm not sure whether this feature 
has been released). It will list the select groups on your system and their 
current settings. If any of those settings corresponds to a port you have 
uninstalled, you should be able to remove the symlinks with

sudo port select --set python none
sudo port select --set python2 none
sudo port select --set python3 none
etc etc etc

> I wonder what causes this kind of problem? I cannot remember any of my port 
> processes terminating incorrectly. I have lately been uninstalling 
> python-related ports, because I had too many different versions of python on 
> my machine, and I was getting confused.

The symlinks created by "port select" are not modified if the selected port is 
subsequently deactivated or uninstalled. I think there is an open ticket about 
this, but I can't find it at the moment.

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


MacPorts missing links

2016-09-10 Thread David Epstein
I gave the command:

ls -l /opt/local/bin/py*
and the system replied:

> lrwxr-xr-x  1 root  wheel  23  9 Jun 19:13 /opt/local/bin/pydoc@ -> 
> /opt/local/bin/pydoc2.7
> lrwxr-xr-x  1 root  wheel  23  9 Jun 17:19 /opt/local/bin/pydoc3@ -> 
> /opt/local/bin/pydoc3.5
> lrwxr-xr-x  1 root  wheel  24  9 Jun 19:13 /opt/local/bin/python@ -> 
> /opt/local/bin/python2.7
> lrwxr-xr-x  1 root  wheel  31  9 Jun 19:13 /opt/local/bin/python-config@ -> 
> /opt/local/bin/python2.7-config
> lrwxr-xr-x  1 root  wheel  24  9 Jun 17:19 /opt/local/bin/python3@ -> 
> /opt/local/bin/python3.5
> lrwxr-xr-x  1 root  wheel  31  9 Jun 17:19 /opt/local/bin/python3-config@ -> 
> /opt/local/bin/python3.5-config
> lrwxr-xr-x  1 root  wheel  25  9 Jun 17:19 /opt/local/bin/python3m@ -> 
> /opt/local/bin/python3.5m
> lrwxr-xr-x  1 root  wheel  32  9 Jun 17:19 /opt/local/bin/python3m-config@ -> 
> /opt/local/bin/python3.5m-config
> lrwxr-xr-x  1 root  wheel  25  9 Jun 19:13 /opt/local/bin/pythonw@ -> 
> /opt/local/bin/pythonw2.7
> lrwxr-xr-x  1 root  wheel  25  9 Jun 17:19 /opt/local/bin/pyvenv@ -> 
> /opt/local/bin/pyvenv-3.5

You will see that none of the files on the righthand side of the arrow -> 
appears on any lefthand side. I tried “port provides” on both lefthand and 
righthand sides and received error messages from port such as
> /opt/local/bin/pydoc2.7 does not exist.

and
> /opt/local/bin/pydoc is not provided by a MacPorts port.


How do I get rid of the symbolic links, other than using /bin/rm, something I 
have been told never to do?

How can I find all hanging links like this in /opt? Presumably there is a 
clever formula using unix find.

I wonder what causes this kind of problem? I cannot remember any of my port 
processes terminating incorrectly. I have lately been uninstalling 
python-related ports, because I had too many different versions of python on my 
machine, and I was getting confused.

David Epstein






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