Re: macports without XCode
/ Craig Treleaven wrote on Wed 7.Nov'12 at 9:37:41 -0400 / At 2:11 PM + 11/7/12, Federico Calboli wrote: On 7 Nov 2012, at 14:06, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: Which packages if I can ask? because they might be packages that I do not want nor need. I grepped to find 148 packages using our xcode includes explicitly (xcode.*1\.0). There may be more that were manually built without using our PortGroup files. Unless these packages are essential to using macports, and thus unavoidable, 148 packages are a trivial percentage of the packages provided by macports. Couldn't I just avoid them altogether? How so? I would have imagined it's the CLT that make the difference, after all they mast be installed for macports. ...and Xcode must also be installed. We do version detection using `xcodebuild -version` (see zlib for an example). We would need an alternative to this if it's not installed. That's fine, and as I said I accept the space penalty of having to have Xcode, but I fail to see why the versioning could not be done on clang or llvm (or whatever thing is in the CLT package that could be used for this) I believe support is a big issue. It is hard enough for a port maintainer to test with multiple versions of XCode. Expanding that to multiple versions of the command line tools would make it that much worse. Requiring the full XCode install isn't a big burden for users. Things might be different if Apple was charging a non-trivial amount of money for XCode. Craig I haven't looked for ages but is the OpenDarwin project still going? I had thoughts once upon-a-time that this project might get going well enough to provide an entire Open Source platform that macports would be a great candidate for being the default package manager on; thus providing a complete OS environment that breaks away from Apple completely. Given the direction it looks like they're going in that would be fantastic. I wonder if something like that would ever happen. I've decided to stay at 10.7.x and not make the change Mountain Lion or beyond, I think someone else mentioned they were doing something similar on this list recently. But back on topic - I don't feel that having to install Xcode is a major problem really. I mean it's massive and takes an age to download but still. Especially as it would no doubt cause too much work to restructure macports to do without it. Even if one wants to build software from source without macports they still require the Xcode installation to do so. It's a good question though but I wouldn't bother giving yourself the headache of trying to work around it by not installing Xcode. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: macports without XCode
On Nov 08, 2012, at 01:29 PM, "William H. Magill" mag...@icloud.com wrote:On Nov 07, 2012, at 08:47 AM, Federico Calboli f.calb...@gmail.com wrote:After having a go with homebrew I decided that macport's use of /opt/local is significantly less likely to screw up my system, so I am now quite firmly on the macport side of the camp. One good thing homebrew has though is the fact it only requires the command line tools, not the whole Xcode installation. Is a macports -Xcode +CLT ever going to happen?I do not believe it is possible to acquire/install the Command Line Tools (CLT) WITHOUT first installing Xcode. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: macports without XCode
On 8 Nov 2012, at 18:29, William H. Magill mag...@icloud.com wrote: On Nov 07, 2012, at 08:47 AM, Federico Calboli f.calb...@gmail.com wrote: After having a go with homebrew I decided that macport's use of /opt/local is significantly less likely to screw up my system, so I am now quite firmly on the macport side of the camp. One good thing homebrew has though is the fact it only requires the command line tools, not the whole Xcode installation. Is a macports -Xcode +CLT ever going to happen? I do not believe it is possible to acquire/install the Command Line Tools (CLT) WITHOUT first installing Xcode. It is, people using homebrew (and not just them) do it all the time. BW F -- Federico Calboli f.calb...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
How to find which port a file belong to?
Hi!
I often get into this issue where I have a file under /opt/local
and want to know which port that file belong to. I read through
port man file and Google about it but I cannot seems to find any
solution.
Any thought?
Thanks!
--
(stephan paul) Arif Sahari Wibowo
/___ /___/ /___/ /___ http://www.arifsaha.com/
/ / / / /
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to find which port a file belong to?
I often get into this issue where I have a file under /opt/local and want to know which port that file belong to. I read through port man file and Google about it but I cannot seems to find any solution. port contents FULL_PATH_OF_FILE like so: port contents /opt/local/bin/pspp ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to find which port a file belong to?
Wow, wrong word there! Sorry port provides FILENAME the opposite is port contents PORTNAME ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to find which port a file belong to?
On 2012-11-08, 12:43, Jeremy Lavergne wrote:
port provides FILENAME
Ah Ok, I guess somehow I missed that from the port manual.
Thanks!
--
(stephan paul) Arif Sahari Wibowo
/___ /___/ /___/ /___ http://www.arifsaha.com/
/ / / / /
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Re: macports without XCode
On Nov 8, 2012, at 02:12, Jamie Paul Griffin wrote: I haven't looked for ages but is the OpenDarwin project still going? I had thoughts once upon-a-time that this project might get going well enough to provide an entire Open Source platform that macports would be a great candidate for being the default package manager on; thus providing a complete OS environment that breaks away from Apple completely. Given the direction it looks like they're going in that would be fantastic. I wonder if something like that would ever happen. I've decided to stay at 10.7.x and not make the change Mountain Lion or beyond, I think someone else mentioned they were doing something similar on this list recently. The OpenDarwin project was ended in 2006, at which time the DarwinPorts project changed its name to MacPorts to indicate its focus on Apple's commercial Mac OS X operating system, as opposed to any open-source efforts based on the underlying Darwin OS. OS X remains our focus today. https://trac.macports.org/wiki/MacPortsHistory ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to compile all my package as 64 bit architecture by default ?
Hello, I work with os x 10.8.2. Need I configure something ? Tanks by advance for your answer Best regards mparchet Le 7 nov. 2012 à 21:18, Michaël Parchet mparc...@sunrise.ch a écrit : Hello, I would like to recompile all my packages as 64 bit by. And I would like configure macport to compile as 64 bit by default I need to use kdelib and kdepim4 witch is compiled as 32 bit. Can you help me please. Best regards mparchet ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to compile all my package as 64 bit architecture by default ?
On Thu, Nov 8, 2012 at 4:53 PM, Michaël Parchet mparc...@sunrise.ch wrote: I work with os x 10.8.2. 10.8.2 is only capable of producing and running 64-bit packages normally, so you shouldn't have to do anything. If you have 32-bit packages, the usual reason is because you started out on an earlier OS X version and didn't follow the instructions at https://trac.macports.org/wiki/Migration . -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix/linux, openafs, kerberos, infrastructure http://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: any way to use OS 10.3.9?
On Nov 8, 2012, at 8:18 PM, David Prager Branner brannerchin...@gmail.com wrote: I was able to install and build Macports 1.710, apparently without problems, but on the initial sudo port -v selfupdate I get what appears to be a fatal error: Command output: checking build system type... powerpc-apple-darwin7.9.0 checking host system type... powerpc-apple-darwin7.9.0 checking target system type... powerpc-apple-darwin7.9.0 checking MacPorts version... 2.1.2 port selfupdate updates the ports tree, but it also tries to update MacPorts base to the latest version (currently 2.1.2). You might want to try running port sync instead. http://guide.macports.org/chunked/using.html#using.port.sync vq ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: any way to use OS 10.3.9?
On Nov 8, 2012, at 20:28, Lawrence Velázquez larry.velazq...@gmail.com wrote:
On Nov 8, 2012, at 8:18 PM, David Prager Branner brannerchin...@gmail.com
wrote:
I was able to install and build Macports 1.710, apparently without problems,
but on the initial
sudo port -v selfupdate
I get what appears to be a fatal error:
Command output: checking build system type... powerpc-apple-darwin7.9.0
checking host system type... powerpc-apple-darwin7.9.0
checking target system type... powerpc-apple-darwin7.9.0
checking MacPorts version... 2.1.2
port selfupdate updates the ports tree, but it also tries to update
MacPorts base to the latest version (currently 2.1.2). You might want to try
running port sync instead.
http://guide.macports.org/chunked/using.html#using.port.sync
Running sudo port sync is out too, because that will update the ports to the
current version, which will not be compatible with old versions of MacPorts. If
you want to use an old version of MacPorts (which is the only option for
Panther and older), you must use correspondingly old portfiles, and then never
update your ports.
You can get an archive of ports from December 14, 2008, from the day MacPorts
1.7.0 was released, here:
https://svn.macports.org/repository/macports/downloads/MacPorts-1.7.0/
Using that, you could install the subversion port, then you could get somewhat
newer ports from the Subversion repository. For example to check out ports from
the day before 1.8.0 was released:
svn co https://svn.macports.org/repository/macports/trunk/dports -r
'{2009-08-28}'
As you get newer than that, more and more ports won't work with MacPorts 1.7
because they'll contain keywords that older versions of MacPorts won't
understand and will consider syntax errors. Plus, we've already been having
trouble with many ports not building on Tiger, so they surely won't build on
Panther either.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Fwd: any way to use OS 10.3.9?
Forwarding to the list. Looks like you're already running into the incompatible-portfiles problem that Ryan brought up. vq Begin forwarded message: From: David Prager Branner brannerchin...@gmail.com Subject: Re: any way to use OS 10.3.9? Date: November 8, 2012 10:03:11 PM EST To: Lawrence Velázquez larry.velazq...@gmail.com Thanks — that worked. However, I now find that when trying to install mercurial I get the error invalid command name license and in the list archives I see references to this being fixed only in v. 1.8.1 . I don't think 1.8.1 will run on OS 10.3.9, though, right? - dpb ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: any way to use OS 10.3.9?
David Prager Branner brannerchin...@gmail.com wrote: I have OS 10.3.9 on an old iBook, with Xcode v. 1.5 installed. No higher versions of the OS can be installed on this hardware. I was able to install and build Macports 1.710, apparently without problems, but on the initial sudo port -v selfupdate I get what appears to be a fatal error: Command output: checking build system type... powerpc-apple-darwin7.9.0 checking host system type... powerpc-apple-darwin7.9.0 checking target system type... powerpc-apple-darwin7.9.0 checking MacPorts version... 2.1.2 checking for sw_vers... /usr/bin/sw_vers checking for defaults... /usr/bin/defaults checking for xcode-select... no checking Mac OS X version... 10.3.9 configure: error: This version of Mac OS X is not supported Please upgrade at http://store.apple.com/ Are there any options I can use to enable even partial compatibility with my ancient system? Or am I sunk? It may be feasible, but no guarantees. You would have to meet the prerequisites for the current version of MacPorts. 1. SQLite. Panther doesn't ship with it. You'd have to install a version at least as new as the one that ships with Tiger, though a newer version would be better if possible. 2. Tcl 8.4+. I forget which version of Tcl Panther has, but if it's 8.4, you'll need to install 8.4.x or 8.5.x. You need tcl threads enabled. 3. You would then need to install MacPorts from source. You'd first need to edit configure.ac to remove 10.3 from the list of unsupported versions, and then run ./regen.sh (hopefully you have autoconf? If not you'd have to just edit the configure script directly.) Then you need to use configure args to indicate where your SQLite and possibly Tcl installations are located. There may be other problems with base. There are definitely problems with many ports. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: any way to use OS 10.3.9?
Ryan Schmidt ryandes...@macports.org wrote:
You can get an archive of ports from December 14, 2008, from the day MacPorts
1.7.0 was released, here:
https://svn.macports.org/repository/macports/downloads/MacPorts-1.7.0/
Using that, you could install the subversion port, then you could get
somewhat newer ports from the Subversion repository. For example to check out
ports from the day before 1.8.0 was released:
svn co https://svn.macports.org/repository/macports/trunk/dports -r
'{2009-08-28}'
Getting
https://distfiles.macports.org/MacPorts/MacPorts-1.8.0-archive.tar.bz2
would be easier and virtually the same (compatible with 1.7.1), since
the archive tarballs are generated just before the corresponding base
version is released.
- Josh
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Re: any way to use OS 10.3.9?
On Nov 8, 2012, at 22:06, Joshua Root j...@macports.org wrote:
Ryan Schmidt ryandes...@macports.org wrote:
You can get an archive of ports from December 14, 2008, from the day
MacPorts 1.7.0 was released, here:
https://svn.macports.org/repository/macports/downloads/MacPorts-1.7.0/
Using that, you could install the subversion port, then you could get
somewhat newer ports from the Subversion repository. For example to check
out ports from the day before 1.8.0 was released:
svn co https://svn.macports.org/repository/macports/trunk/dports -r
'{2009-08-28}'
Getting
https://distfiles.macports.org/MacPorts/MacPorts-1.8.0-archive.tar.bz2
would be easier and virtually the same (compatible with 1.7.1), since
the archive tarballs are generated just before the corresponding base
version is released.
Good point!
Using a Subversion working copy would give you more control over updating
individual ports to newer versions, for those where that might be possible.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
