Re: Distinguishing between deactivated ports than I want to keep and outdated port I no longer care about
On Feb 24, 2016, at 1:45 AM, Mojca Miklavec wrote: > I now tried running >sudo port uninstall inactive and not requested > This seems to basically work, but it fails when an inactive > unrequested port is a dependency of another inactive requested port. > (Or at least that's what I suspect is happening.) That sounds plausible. > Is there any equivalent of "port installed" that also shows whether a > port was requested No, but you can show installed requested ports with "port installed requested" and installed unrequested ports with "port installed unrequested". If you want a combined list you could use: (port -q installed requested | sed 's/$/ (requested)/' && port -q installed unrequested | sed 's/$/ (unrequested)/') | sort > and the size of .tar.bz2 with binaries? To see the disk space used by the installed files of a port, you can use: port space name-of-port I'm not sure if that includes the size of the .tbz2 archive file. To get that separately, you can look at: ls -l /opt/local/var/macports/software/name-of-port/ ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Distinguishing between deactivated ports than I want to keep and outdated port I no longer care about
On 23 February 2016 at 21:38, Ryan Schmidt wrote: > On Feb 23, 2016, at 1:43 PM, Mojca Miklavec wrote: > >> I often deactivate certain "heavy" ports where I want to play with >> different versions or variants. Sometimes I deactivate clang 3.8 when >> I don't feel like waiting for the long recompilation of the latest and >> greatest new version (that will be outdated again in a few days >> anyway) or when a newer version no longer works/compiles. Sometimes I >> deactivate universal ports. Those are generally the ports I want to >> keep for some time. >> >> But I would like to save space and uninstall other ports that I don't >> particularly care about (which have been superseded by newer >> versions). >> >> Is there any way to flag a certain set of inactive ports that I >> specifically want to keep even after "sudo port uninstall inactive >> [and somethingelse]"? > > The way to flag a port as wanted is: > > sudo port setrequested name-of-port > > The way to flag a port as not wanted is: > > sudo port unsetrequested name-of-port > > Or: > > sudo port setunrequested name-of-port > > Then you can use the "requested" and "unrequested" pseudoports when selecting > ports: > > sudo port uninstall inactive and unrequested > > This would apply to all variants and versions of a given port name, however. > There is no provision for, for example, marking the non-universal version of > a port requested while marking the universal version of that same port as > unrequested. Thank you. I now tried running sudo port uninstall inactive and not requested This seems to basically work, but it fails when an inactive unrequested port is a dependency of another inactive requested port. (Or at least that's what I suspect is happening.) Is there any equivalent of "port installed" that also shows whether a port was requested and the size of .tar.bz2 with binaries? Mojca ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [145995] trunk/dports/www/wp-cli/Portfile
> On Feb 23, 2016, at 7:14 PM, take...@macports.org wrote: > > Revision > 145995 > Author > take...@macports.org > Date > 2016-02-23 17:14:08 -0800 (Tue, 23 Feb 2016) > Log Message > > wp-cli: add run-time dependency to php binary > Modified Paths > > • trunk/dports/www/wp-cli/Portfile > > +depends_run bin:php:php70 The php70 port doesn't provide a php binary; it provides a php70 binary. So if wp-cli is expecting a php binary, php70 by itself is not enough to provide that. The user would have to run "sudo port select php php70" to get a php symlink pointing to the php70 binary. OS X has shipped with /usr/bin/php for a long time, so hopefully that's enough for all OS X users. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Request for help/comments about patches for wxWidgets
Hi, I would like to have a port for KiCad in MacPorts. Upstream (= KiCad) provides a number of patches for wxWidgets, but I don't understand them all and would be grateful for some basic review & help from those who might understand them, so that we can make an informed decision about which patches to apply (and to which OS versions). Aljaž has a Portfile for KiCad basically ready, but we would need to fix the problems from wxWidgets first. I opened a ticket: - https://trac.macports.org/ticket/50701 and would be grateful for additional feedback, in particular about those patches that are not yet included upstream (in wxWidgets). (Build instructions on the KiCad website only mention five out of ten patches, but the build scripts use all of them.) Thank you, Mojca ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Sonarqube portfile addition
Hi all, I’d created a ticket for adding a basic Sonarqube installation: https://trac.macports.org/ticket/49517 It’s my first attempt at creating a portfile for distribution, so if there’s any things that could be improved please let me know. cheers, Lachlan ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Distinguishing between deactivated ports than I want to keep and outdated port I no longer care about
On Feb 23, 2016, at 1:43 PM, Mojca Miklavec wrote: > I often deactivate certain "heavy" ports where I want to play with > different versions or variants. Sometimes I deactivate clang 3.8 when > I don't feel like waiting for the long recompilation of the latest and > greatest new version (that will be outdated again in a few days > anyway) or when a newer version no longer works/compiles. Sometimes I > deactivate universal ports. Those are generally the ports I want to > keep for some time. > > But I would like to save space and uninstall other ports that I don't > particularly care about (which have been superseded by newer > versions). > > Is there any way to flag a certain set of inactive ports that I > specifically want to keep even after "sudo port uninstall inactive > [and somethingelse]"? The way to flag a port as wanted is: sudo port setrequested name-of-port The way to flag a port as not wanted is: sudo port unsetrequested name-of-port Or: sudo port setunrequested name-of-port Then you can use the "requested" and "unrequested" pseudoports when selecting ports: sudo port uninstall inactive and unrequested This would apply to all variants and versions of a given port name, however. There is no provision for, for example, marking the non-universal version of a port requested while marking the universal version of that same port as unrequested. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Distinguishing between deactivated ports than I want to keep and outdated port I no longer care about
I don't think there's such a way to flag certain ports, but I'd love to see it in place for exactly the reasons Mojca describes -- especially for the purposes of "reclaim". - MLD On Tue, Feb 23, 2016, at 02:43 PM, Mojca Miklavec wrote: > I often deactivate certain "heavy" ports where I want to play with > different versions or variants. Sometimes I deactivate clang 3.8 when > I don't feel like waiting for the long recompilation of the latest and > greatest new version (that will be outdated again in a few days > anyway) or when a newer version no longer works/compiles. Sometimes I > deactivate universal ports. Those are generally the ports I want to > keep for some time. > > But I would like to save space and uninstall other ports that I don't > particularly care about (which have been superseded by newer > versions). > > Is there any way to flag a certain set of inactive ports that I > specifically want to keep even after "sudo port uninstall inactive > [and somethingelse]"? ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Distinguishing between deactivated ports than I want to keep and outdated port I no longer care about
Hi, I often deactivate certain "heavy" ports where I want to play with different versions or variants. Sometimes I deactivate clang 3.8 when I don't feel like waiting for the long recompilation of the latest and greatest new version (that will be outdated again in a few days anyway) or when a newer version no longer works/compiles. Sometimes I deactivate universal ports. Those are generally the ports I want to keep for some time. But I would like to save space and uninstall other ports that I don't particularly care about (which have been superseded by newer versions). Is there any way to flag a certain set of inactive ports that I specifically want to keep even after "sudo port uninstall inactive [and somethingelse]"? Thank you, Mojca ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
