Re: Remove port

2016-01-09 Thread Ryan Schmidt

On Jan 8, 2016, at 11:35 PM, Eitan Adler wrote:
> 
> On 5 January 2016 at 11:05, Ryan Schmidt wrote:
>> 
>> If you're interested in removing those dependencies that are no longer 
>> needed, examine the list of ports produced by:
>> 
>> port installed leaves
>> 
>> and, if you like, uninstall them with:
>> 
>> sudo port uninstall leaves
> 
> wouldn't
> port uninstall leaves and unrequested
> be slightly better here since some leaf ports are actually wanted?

According to port(1) leaves are "installed ports that are unrequested and have 
no dependents". So if you requested a port, it is by definition not a leaf.

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


Re: XFCE

2016-01-09 Thread Anders F Björklund
Pierre Henri CHAUDOUARD wrote:

> What is the role of xfce4-session ? Because other components (xfwm4, panel, 
> desktop) seem to work ...
> 
>>> /opt/local/etc/xdg/xfce4/xinitrc: line 113: 13661 Segmentation fault: 11 
>>> xfce4-session
>>>  
>>  This segfault needs to be debugged by someone. Thank you for trying it out, 
>> none the less!

According to the home page of the upstream project, , the 
Xfce Session Manager:
"Controls the login and power management of the desktop and allows you to store 
multiple login sessions."

See: https://en.wikipedia.org/wiki/X_session_manager

To fix, "someone" needs to build a debugging version of xfce4-session and run 
it with a debugger.
On the captain (OS X 10.11). That will give one a stack trace and a code 
reference to to go on...

File a bug: http://guide.macports.org/#project.tickets


"In general, application bugs should be reported to the developers of the app 
(“upstream”), not MacPorts."
But I think it's safe to say that no-one* is running Xfce on Darwin/XQuartz, so 
this is Terra Incognita...

Anyway, the bug tracker is: https://bugzilla.xfce.org/

* the jury is still out on "why would anyone want to do that", even though it 
"should" still be possible.
For most normal users, something like VirtualBSD would probably be a better 
option. Or at least packages.

See http://www.dedoimedo.com/computers/virtualbsd.html

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


Re: app-bundle vs. regular/"BSD utility" executables : what differences are there still?

2016-01-09 Thread René J . V . Bertin
On Tuesday January 05 2016 10:29:41 Jeremy Huddleston Sequoia wrote:

>It's possible for a standalone executable to have an Info.plist.  It is 
>embedded in the executable in an __info_plist section.  This can be done by 
>the CREATE_INFOPLIST_SECTION_IN_BINARY Xcode build setting or by creating an 
>__info_plist section manually at link time if not using Xcode 
>(-Wl,-sectcreate,__TEXT,__info_plist,/path/to/my/Info.plist).

I've tried to read up on this way of "bundling" an Info.plist, but all I've 
found to date is focused on info dicts that are intended only (chiefly?) for 
allowing an executable to be code-signed. I haven't found any discussion of the 
elements that are supported. It seems safe to assume that a list of document 
types will simply be ignored, though maybe not the references it makes to 
document icons. The bundle icon idem: is that key ignored when present in an 
embedded Info.plist, or if not, where is the icon expected to be found?

All this because there is a CMake macro (in the ECM, "Extra CMake Modules") 
that makes it trivial to switch the target between an app bundle and a 
traditional executable. The app bundle gets a standard Info.plist with the 
proper key/value pairs (including the app icon if one is defined in the CMake 
file). It'd probably be easiest if that plist can be embedded.

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


Re: Remove port

2016-01-09 Thread Eitan Adler
On 9 January 2016 at 03:51, Ryan Schmidt  wrote:
>
> On Jan 8, 2016, at 11:35 PM, Eitan Adler wrote:
>>
>> On 5 January 2016 at 11:05, Ryan Schmidt wrote:
>>>
>>> If you're interested in removing those dependencies that are no longer 
>>> needed, examine the list of ports produced by:
>>>
>>> port installed leaves
>>>
>>> and, if you like, uninstall them with:
>>>
>>> sudo port uninstall leaves
>>
>> wouldn't
>> port uninstall leaves and unrequested
>> be slightly better here since some leaf ports are actually wanted?
>
> According to port(1) leaves are "installed ports that are unrequested and 
> have no dependents". So if you requested a port, it is by definition not a 
> leaf.

Ah - I didn't realize that.  a bit of a thread hijack but how would
one list ports that have zero dependents (requested or not)?



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


Trouble with Macports Install - 2014 Mac Mini running El Capitan

2016-01-09 Thread Steve Sharpe
I downloaded 'mythtv-pkg.27-Fixes-0.27.4-20150304.mpkg' from the website and 
installed it without issue.  However, when I get to the first “paste” entry to 
begin initializing the database (paste sudo -u _mysql mysql_install_db into a 
Terminal window), I’m prompted for a password.  The ‘mythtv’ password doesn’t 
work.  Pressing enter for a blank password doesn’t work either.  I confirmed 
that the default config.xml file located in the .mythtv folder is unchanged 
(shows both username and password as ‘mythtv’).  I tried removing the Macports 
app folder and deleted both the .mythtv and /opt/ folders and reinstalled 
Macports from the downloaded .mpkg file.  No change in the password issue.  Any 
advice???___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: Trouble with Macports Install - 2014 Mac Mini running El Capitan

2016-01-09 Thread Craig Treleaven

> On Jan 9, 2016, at 12:01 PM, Steve Sharpe  
> wrote:
> 
> I downloaded 'mythtv-pkg.27-Fixes-0.27.4-20150304.mpkg' from the website and 
> installed it without issue.  However, when I get to the first “paste” entry 
> to begin initializing the database (paste sudo -u _mysql mysql_install_db 
> into a Terminal window), I’m prompted for a password.  The ‘mythtv’ password 
> doesn’t work.  Pressing enter for a blank password doesn’t work either.  I 
> confirmed that the default config.xml file located in the .mythtv folder is 
> unchanged (shows both username and password as ‘mythtv’).  I tried removing 
> the Macports app folder and deleted both the .mythtv and /opt/ folders and 
> reinstalled Macports from the downloaded .mpkg file.  No change in the 
> password issue.  Any advice???

You need to use the OS X admin password—the same one you use for installing 
other software.  

‘sudo’ causes the following command to be executed as the “superuser”.  For 
this particular command, we need superuser privileges in order to create the 
initial, blank database that MythTV will eventually use.

HTH,

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


Re: list port with no dependents (was: Re: Remove port)

2016-01-09 Thread Ryan Schmidt

On Jan 9, 2016, at 11:38 AM, Eitan Adler wrote:

> On 9 January 2016 at 03:51, Ryan Schmidt wrote:
> 
>> According to port(1) leaves are "installed ports that are unrequested and 
>> have no dependents". So if you requested a port, it is by definition not a 
>> leaf.
> 
> Ah - I didn't realize that.  a bit of a thread hijack but how would
> one list ports that have zero dependents (requested or not)?

I don't know, but why do you want to know that?

Your installed ports are there either because you requested them (you need and 
care about these ports), or because something you requested needed them (you 
indirectly need but don't directly care about these ports), or because they're 
left over from something that used to be installed that needed them (you don't 
need or care about these ports).

You're asking if there's a way to list the port you need but don't care about. 
I'm not sure if there's a command for that.

You can use "port installed requested" to see the list of ports you requested. 
If anything in the list is not something you actually want, you can mark it as 
not requested by using "sudo port unsetrequested PORTNAME".

You can use "port installed leaves" to see the list of ports you didn't request 
that aren't needed by anything. If anything in the list is something you 
actually want, you can mark it as requested by using "sudo port setrequested 
PORTNAME".

Finally, you can uninstall the ports you really don't need by using "sudo port 
uninstall leaves".


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


Re: XFCE

2016-01-09 Thread James Linder

> On 10 Jan 2016, at 4:00 AM, macports-users-requ...@lists.macosforge.org wrote:
> 
>> What is the role of xfce4-session ? Because other components (xfwm4, panel, 
>> desktop) seem to work ...
>> 
 /opt/local/etc/xdg/xfce4/xinitrc: line 113: 13661 Segmentation fault: 11 
 xfce4-session
 
>>> This segfault needs to be debugged by someone. Thank you for trying it out, 
>>> none the less!
> 
> According to the home page of the upstream project, , 
> the Xfce Session Manager:
> "Controls the login and power management of the desktop and allows you to 
> store multiple login sessions."
> 
> See: https://en.wikipedia.org/wiki/X_session_manager
> 
> To fix, "someone" needs to build a debugging version of xfce4-session and run 
> it with a debugger.
> On the captain (OS X 10.11). That will give one a stack trace and a code 
> reference to to go on...
> 
> File a bug: http://guide.macports.org/#project.tickets
> 
> 
> "In general, application bugs should be reported to the developers of the app 
> (?upstream?), not MacPorts."
> But I think it's safe to say that no-one* is running Xfce on Darwin/XQuartz, 
> so this is Terra Incognita...
> 
> Anyway, the bug tracker is: https://bugzilla.xfce.org/
> 
> * the jury is still out on "why would anyone want to do that", even though it 
> "should" still be possible.
> For most normal users, something like VirtualBSD would probably be a better 
> option. Or at least packages.
> 
> See http://www.dedoimedo.com/computers/virtualbsd.html

Pierre to add to comments above 
I’m a great fan of xfce and run that on my many linux machines.
Ideologically I hate apple, but apple make their hardware and software play 
together very nicely e.g. bluetooth at boot, e.g. nice sound from their crappy 
speakers e.g. heat from core sleep vs (hot) heat from core throttle e.g. the 
wireless on my mac mini is perfect under OS X but rather iffy under any linux 
distos that I have tried.

After playing with xfce on the mac mini for a few days the only benefits I 
could find were having X11 all the time (subtle reasons) and xfce4-terminal. 
iTerm does a pretty equivalent job.

So I have to conclude that my mac(s) do exactly what I need, that mac ports is 
the glue that turns this into plain sailing and the xfce port is very 
interesting, but for me, what’s the point. Clementine (not mac ports) even 
plays my oggs.
James

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