Porticus 1.8 Released
This release some new features and improves support for MacPorts 1.8.
- Improve MacPorts 1.8 support (update and uninstall options)
- Added menu option to uninstall all inactive ports.
- Added more options to clean command.
- Cmd-Opt-F now moves directly to the search/filter field.
You can get Porticus 1.8 here.
I hope to get some documentation up on the website soon so stay tuned.
November 20th, 2009 at 9:09 am
Hi, this is a nice GUI. Unfortunately it doesn’t show any information about inactive ports: they are listed as active.
Here are some suggestions:
- Add a new colour for installed but inactive ports (suggestion: grey or light blue). It should have precedence over the red outdated colour.
- Add a new smart group for Active ports, and one for Inactive.
- Inactive ports shouldn’t have “Active Version” in their information.
November 20th, 2009 at 9:14 am
Oops, I found a minor bug:
I have iso-codes 3.11_0 installed and the latest version is 3.11.1_0, but it is NOT listed as outdated in Porticus. (But it is on the command line).
November 20th, 2009 at 6:21 pm
All installed versions are listed in the port details but Porticus doesn’t currently know which version is active, this is a long standing issue. I know two ways to fix it which is good but I haven’t had time to do either yet. Watch this space…
November 21st, 2009 at 6:32 am
I have seen Porticus generate a bad command line when I’m trying to do an upgrade.
It looks the options are being concatenated, rather than being separated by spaces
port -dnR-force-enforce-variants upgrade boost +doc +debug
November 21st, 2009 at 8:25 am
What version of Porticus was running and where was the message output to? The string would indicate that the options are in the wrong order as well, version 1.7 had a bug on MacPorts 1.8 with the flag order. The generated string in the message window has little relationship to the actual command – the spaces are irrelevant. I will have a look and see if I can reproduce this.
December 14th, 2009 at 3:06 am
Porticus is suddenly crashing for me on every start, at around the point when it sorts the list of installed ports with what is outdated
December 14th, 2009 at 3:10 am
Not really helping with the above message, I guess
The apple crash report is at http://pastebin.com/m63069f3f
It fails in parsing the list at about 75% or so
December 14th, 2009 at 7:12 am
Thanks for the bug report. I will investigate. What MacPorts version are you running? Any non-standard configuration?
Just did a selfupdate here and needless to say it works fine
Thanks for sending the link to the crash log. Would you be willing to try a beta version with debug enabled? Let me know at support @ alittledrop.com
December 15th, 2009 at 12:17 am
Don’t know if this is the same problem, but when I start Porticus 1.8 it hangs when it says “Parsing ports list ….” (the whole machine becomes almost non-responsive, but as far as I can tell there is almost no CPU-usage. Very strange). “port list” etc from the command line work without problem, but maybe it is a problem with the special options to the port command. Which options would that be? Is there any other information I can provide? Is there another way to provide bug-reports than posting them here?
December 15th, 2009 at 6:30 pm
This is not likely to be the same issue but you never know. THere are no special options to self update used by Porticus (you can set the debug option in the preferences and see if there are any messages in the Console or Porticus log files). I am not aware of anything the Porticus could be doing to make you Mac unresponsive and would b e really interested in finding out. If you have any Console log or Porticus log details could you please send them to me or post them here.
Thanks.
Richard
December 16th, 2009 at 11:23 pm
Didn’t find your mail (didn’t search to much though)
The console log during running is (Last one is from the forceful termination)
09.12.16 11:03:18 Porticus[627] Version 1.8 or later detected
09.12.16 11:03:18 Porticus[627] Exception raised during posting of notification. Ignored. exception: ‘+entityForName: could not locate an NSManagedObjectModel for entity name ‘MacPorts” invoked observer method: ‘*** -[Porticus_AppDelegate applicationDidFinishLaunching:]‘ observer: 0x42e9a0 notification name: ‘NSApplicationDidFinishLaunchingNotification’
09.12.16 11:03:59 com.apple.launchd.peruser.502[177] ([0x0-0x53053].com.alittledrop.Porticus[627]) Exited: Terminated
After I did a
sudo port -d sync
the problem went away
Bernhard
December 17th, 2009 at 6:10 pm
Thanks for the update, it would be nice to know why the sync fixed the issue though.
December 29th, 2009 at 10:09 am
“Follow dependents” checkbox in uninstall window does not work for me.
I get error message:
Port command started with PID 60431
Unable to uninstall expat 2.0.1_0, the following ports depend on it:
gettext
Error: port uninstall failed: Please uninstall the ports that depend on expat first.
Executing: /opt/local/bin/port uninstall expat@2.0.1_0
The command should be something like “/opt/local/bin/port uninstall –follow-dependents expat@2.0.1_0″.
December 29th, 2009 at 10:25 am
I will have a look, are you using the Russian localisation?
December 31st, 2009 at 1:26 am
MD5 of the 1.8.1 version does not match, even after multiple downloads from different locations.
December 31st, 2009 at 5:11 am
I managed to install 1.8.1 via upgrade from 1.8, but when I start Porticus it hangs at “Parsing ports list ….” as @bgschaid already mentioned.
December 31st, 2009 at 8:02 am
The MD5 should be
MD5 (Porticus_1_8_1.dmg) = b41e237170d9d40225fb414a66d32580
This looks correct on the http://porticus.alittledrop.com/download.html page and that is what I get when I download the image. Let me know if you still have a problem.
December 31st, 2009 at 8:05 am
I have not been able to replicate this bug at all, I am still trying. I did add some extra checks to 1.8.1 in the hope of tracking this down. Is there anything written to the Console log when Porticus hangs?