Per package default variants
Hallo. Is there a way to pre-define variants, a certain package should or should not use? Eg. Let's say I'd want to build curl without ssl and with sftp_scp. All other packages should, by default, be built with ssl (if they support it). When manually installing the package, I'd run sudo port install curl -ssl +sftp_scp If I'd want to have all packages without ssl, I'd add -ssl to ~/.macports/variants.conf But that would effect all packages. Well, how to go about it? Thanks a lot, Alexander -- ↯ Lifestream (Twitter, Blog, …) ↣ http://alexs77.soup.io/ ↯ ↯ Chat (Jabber/Google Talk) ↣ a.sk...@gmail.com , AIM: alexws77 ↯ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Octave .m files opening in Xcode
Le 25 sept. 2011 à 15:38, Wesley Davis woda...@aggies.ncat.edu a écrit : I just installed Octave, Gnuplot and Aquaerm using Macports. I installed all three so that I could see the plots of my Ocave scripts. However, now when run my Ocatave .m scripts I get the Xcode application and not the text editor .m is the standard extension for Objective-C source files. No wonder XCode pops up when you double-click them… Vincent ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Octave .m files opening in Xcode
Is there anything that I can do to run my scripts? I see that Macports lists Octave as a port? Or, am I just out of luck? Wes On Sun, Sep 25, 2011 at 9:42 AM, vincent habchi vi...@macports.org wrote: Le 25 sept. 2011 à 15:38, Wesley Davis woda...@aggies.ncat.edu a écrit : I just installed Octave, Gnuplot and Aquaerm using Macports. I installed all three so that I could see the plots of my Ocave scripts. However, now when run my Ocatave .m scripts I get the Xcode application and not the text editor .m is the standard extension for Objective-C source files. No wonder XCode pops up when you double-click them… Vincent ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Octave .m files opening in Xcode
Good Morning Wes, the .m extension is considered to be a C source file. If you do more Octave editing than C/C++, feel free to change the application used to open .m files. J. On Sun, Sep 25, 2011 at 9:46 AM, Wesley Davis woda...@aggies.ncat.eduwrote: Is there anything that I can do to run my scripts? I see that Macports lists Octave as a port? Or, am I just out of luck? Wes On Sun, Sep 25, 2011 at 9:42 AM, vincent habchi vi...@macports.orgwrote: Le 25 sept. 2011 à 15:38, Wesley Davis woda...@aggies.ncat.edu a écrit : I just installed Octave, Gnuplot and Aquaerm using Macports. I installed all three so that I could see the plots of my Ocave scripts. However, now when run my Ocatave .m scripts I get the Xcode application and not the text editor .m is the standard extension for Objective-C source files. No wonder XCode pops up when you double-click them… Vincent ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users -- Jean Gobin, CCENT, CCNA, CCNA Security http://newsfromjean.blogspot.com/ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Octave .m files opening in Xcode
On Sep 25, 2011, at 09:59, Jean-Francois Gobin wrote: the .m extension is considered to be a C source file. If you do more Octave editing than C/C++, feel free to change the application used to open .m files. Right. And instructions for doing that are in Apple's knowledge base: http://support.apple.com/kb/ts2291 The article is old but the section for OS X 10.2/10.3 is still more or less applicable today. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Per package default variants
On Sep 25, 2011, at 03:08, Alexander Skwar wrote: Is there a way to pre-define variants, a certain package should or should not use? Eg. Let's say I'd want to build curl without ssl and with sftp_scp. All other packages should, by default, be built with ssl (if they support it). When manually installing the package, I'd run sudo port install curl -ssl +sftp_scp If I'd want to have all packages without ssl, I'd add -ssl to ~/.macports/variants.conf But that would effect all packages. Well, how to go about it? This has been suggested before: https://trac.macports.org/ticket/30328 I still don't see the benefit of it. If you can explain, please do. But I don't see why you don't want to just run: sudo port install curl -ssl +sftp_scp In other words, the install command right there is how you specify that you want specific variants for a specific port. MacPorts will remember those selections across port upgrades. So the only time MacPorts would forget your selected variants is if you deliberately uninstall the port, but if you do that, doesn't that mean you're no longer interested in the port? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
