Re: Ports and their dependencies
On 6/9/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: All jokes aside, would it be helpful to take the great explanations you have all written and integrating them into chapter 5.4.1 of the MacPorts Guide http://guide.macports.org/#reference.dependencies.types? Is this something that would benefit the MacPorts Community (even though I might have been one of the first people to ask such questions explicitly)? I renamed non-port dependencies to file dependencies. See what you think of the revisions in r37493. It can be refined further if necessary. Thanks to Joshua and Ryan for the explanations. http://trac.macports.org/changeset/37493 Mark, that is great, thank you so much. The term file dependencies makes a ton more sense than non-port. And thanks Josh for proof reading the changes Mark made. This makes the MacPorts community ever more stronger! Tabitha Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
Leaving aside the issue of what the best platform for sharing the info might be. If nobody knows it's there, the kick-assingest wiki server the world has or will ever see is not going to address my suggestion in the slightest. My point was that it's quite a challenge finding the current how-to's even if you already know they exist. If you are not in that smallish (I'm guessing--but I've been using *Ports for a fairly long time, and it was a recent message on this list that made me aware) category, then the chances this very useful series of articles will reach the audience that needs it is quite small. Just to refresh, there needs to be a link from the main MacPorts documentation site to the how-to's. As a first step, it's awesome. On Thu, Jun 5, 2008 at 2:22 PM, Jordan K. Hubbard [EMAIL PROTECTED] wrote: On Jun 5, 2008, at 8:42 AM, Lorin Rivers wrote: Awesome! I did not even know about these How To's. You know, it's actually kind of hard to find them, if you don't know about where they are in the first place. I think they deserve more prominence. There should be a link from the documentation area of the main MacPorts site to the HowTo's. I'm still of the opinion that we should install mediawiki on the site and turn these howtos into full-blown, collaboratively maintained reference pages worthy of wikipedia (but, unlike wikipedia, also free to be relevant only in the context of projects hosted at macosforge). What do other folks think? - Jordan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Is MacPort a valid term?
For a long time, I thought that when people were saying port, in this discussion, I thought the were referring to a port or a tcp/ip address. like localhost:80 Clarity is one of the reasons that in the past I frequently used the term MacPorts port (to distinguish it from FreeBSD and other port systems), but this is too cumbersome and inelegant when used a lot so I mostly curtailed that. Using the term MacPort would make the term clear, but is that really a valid term in current usage? It seems we're only comfortable with the plural form, and I think that is why we always fall back to the more generic port to express a single MacPorts port. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Problem with Molden installation
On 10.06.2008, at 16:26, Vincent BOUDON wrote: Thanks a lot, it worked fine. I am really sorry to bother you again with this, but I have another problem with molden on Mac OS X and I must admit that the way to report this via trac.macports.org seems quite obscure to me ... please report it via trac, so we have the records and more people can look at it... Each time I try to add a line in the Z-matrix editor, I get: Segmentation fault i can reproduce this. However, I am sorry, I do not have time to look at this right now. Please report it in trac and to the molden maintainer upstreams Greetings, Jochen -- Einigkeit und Recht und Freiheithttp://www.Jochen-Kuepper.de Liberté, Égalité, FraternitéGnuPG key: CC1B0B4D Sex, drugs and rock-n-roll PGP.sig Description: This is a digitally signed message part ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Problem with Molden installation
Jochen Küpper wrote: On 10.06.2008, at 16:26, Vincent BOUDON wrote: I am really sorry to bother you again with this, but I have another problem with molden on Mac OS X and I must admit that the way to report this via trac.macports.org seems quite obscure to me ... Our guide should shed some light on this, see http://guide.macports.org/#project.tickets Rainer ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
On Tue, Jun 10, 2008 at 12:00 PM, [EMAIL PROTECTED] wrote: Message: 11 Date: Tue, 10 Jun 2008 11:27:30 -0500 From: Lorin Rivers [EMAIL PROTECTED] Subject: Re: New Howto To: Jordan K. Hubbard [EMAIL PROTECTED] Cc: MacPorts Users macports-users@lists.macosforge.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=utf-8 Leaving aside the issue of what the best platform for sharing the info might be. If nobody knows it's there, the kick-assingest wiki server the world has or will ever see is not going to address my suggestion in the slightest. My point was that it's quite a challenge finding the current how-to's even if you already know they exist. If you are not in that smallish (I'm guessing--but I've been using *Ports for a fairly long time, and it was a recent message on this list that made me aware) category, then the chances this very useful series of articles will reach the audience that needs it is quite small. Just to refresh, there needs to be a link from the main MacPorts documentation site to the how-to's. As a first step, it's awesome. Taking up the earlier comment on a need for discussion, what are the pros and cons of the different wiki platforms? I would say, if I had a vote (who does?), that whatever people are willing to use wins. It may not be elegant or state of the art, but the best is the enemy of the good, and good is usually good enough. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
On Jun 10, 2008, at 9:27 AM, Lorin Rivers wrote: Leaving aside the issue of what the best platform for sharing the info might be. If nobody knows it's there, the kick-assingest wiki server the world has or will ever see is not going to address my suggestion in the slightest. Well, to be fair, I thought I was trying to address that by suggesting that there should be a top level doc project - individual projects could point up to it just as easily as it could point down to them, but it would be a clear docs portal for everyone. I know not everyone agrees with this assertion, but I think all the projects on macosforge have more knowledge collectively in common than they think. I then look laterally to the success of projects like wikipedia, which has a knowledge base and contributing community far more vast by comparison, and cannot help but think hmmm.. Just to refresh, there needs to be a link from the main MacPorts documentation site to the how-to's. As a first step, it's awesome. No disagreement at all. Links are cheap, people! Use them! - Jordan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
ThisApp?
This port is no longer? --- Attempting to fetch JHymn_0_9_2_source.zip from http://www.hymn-project.org/download/ --- Attempting to fetch JHymn_0_9_2_source.zip from http://svn.macports.org/repository/macports/distfiles/JHymn --- Attempting to fetch JHymn_0_9_2_source.zip from http://svn.macports.org/repository/macports/distfiles/general/ --- Attempting to fetch JHymn_0_9_2_source.zip from http://svn.macports.org/repository/macports/downloads/JHymn Error: Target org.macports.fetch returned: fetch failed Error: Status 1 encountered during processing. Mack ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
JHymn distfiles (was: Re: ThisApp?)
On Jun 10, 2008, at 15:59, Mack Johnson wrote: This port is no longer? --- Attempting to fetch JHymn_0_9_2_source.zip from http:// www.hymn-project.org/download/ --- Attempting to fetch JHymn_0_9_2_source.zip from http:// svn.macports.org/repository/macports/distfiles/JHymn --- Attempting to fetch JHymn_0_9_2_source.zip from http:// svn.macports.org/repository/macports/distfiles/general/ --- Attempting to fetch JHymn_0_9_2_source.zip from http:// svn.macports.org/repository/macports/downloads/JHymn Error: Target org.macports.fetch returned: fetch failed Error: Status 1 encountered during processing. The developer apparently received a cease and desist order in February 2008 and had to remove the files. http://www.hymn-project.org/forums/viewtopic.php?t=1314 We don't seem to have the files on our mirror either. http://distfiles.macports.org/JHymn/ The forum topic above seems to list some alternatives. Maybe we should remove the JHymn port. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Deluge install issue
On Jun 8, 2008, at 18:09, Joe Schnide wrote: At 6:04 AM -0500 6/8/08, Ryan Schmidt wrote: On Jun 8, 2008, at 05:46, Joe Schnide wrote: I had no problem installing deluge on a MacBookPro but am having a problem on an Intel iMac. What is the difference between the MacBook Pro and the iMac? They're both Intel... Are the both running the same version of Mac OS X yes , Xcode, yes and MacPorts? yes What versions? 10.5.3 Xcode schnide-iMac:~ schnide$ gcc -v Using built-in specs. Target: i686-apple-darwin9 Configured with: /var/tmp/gcc/gcc-5465~16/src/configure --disable- checking -enable-werror --prefix=/usr --mandir=/share/man --enable- languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/ s/$/-4.0/ --with-gxx-include-dir=/include/c++/4.0.0 --with-slibdir=/ usr/lib --build=i686-apple-darwin9 --with-arch=apple --with- tune=generic --host=i686-apple-darwin9 --target=i686-apple-darwin9 Thread model: posix gcc version 4.0.1 (Apple Inc. build 5465) MacPorts 1.600 Is your ports tree up to date? yes (Use sudo port selfupdate to update.) Are the same versions of all dependencies installed? Certainly appear to be so. The Intel iMac was built as a clone of the MacBookPro so they should be pretty close to identical. Hard to know where to start looking then. Certainly there's at least one difference between the two computers: deluge works on one and not the other. :-) I can try installing on 10.5.3 and see what happens. Don't forget to Reply All so your reply goes to the mailing list too, not just to me. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Deluge install issue
On Jun 8, 2008, at 18:09, Joe Schnide wrote: The Intel iMac was built as a clone of the MacBookPro so they should be pretty close to identical. I was recently having difficulties building some ports on my MacBook Pro, but no problems building the same programs on my Mac Pro. (There were problems with the paths when building ports on the laptop.) Both machines have the same versions of Leopard, Xcode, MacPorts, etc. A difference is that when I upgraded from Tiger to Leopard on my Mac Pro, I erased and did a fresh install. On my MacBook Pro, I upgraded from Tiger to Leopard, installing over the previous OS and not deleting a lot of stuff. This past weekend, I removed the entire MacPorts tree and all the other files listed in the MacPorts Guide (and on Trac), and reinstalled MacPorts on my laptop, and I still couldn't build everything I wanted. So, I formatted the laptop hard drive, reinstalled Leopard and I haven't had any problems installing any port. I spent a fair amount of time looking to see what was going on, but could not find the cause. Maybe this issue parallels your two machines? Brian ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: JHymn distfiles
Ryan Schmidt wrote: The developer apparently received a cease and desist order in February 2008 and had to remove the files. http://www.hymn-project.org/forums/viewtopic.php?t=1314 We don't seem to have the files on our mirror either. http://distfiles.macports.org/JHymn/ The forum topic above seems to list some alternatives. Maybe we should remove the JHymn port. If so port hymn should probably go as well (and is equally broken) ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Is MacPort a valid term?
On Jun 10, 2008, at 11:43, [EMAIL PROTECTED] wrote: For a long time, I thought that when people were saying port, in this discussion, I thought the were referring to a port or a tcp/ip address. like localhost:80 Clarity is one of the reasons that in the past I frequently used the term MacPorts port (to distinguish it from FreeBSD and other port systems), but this is too cumbersome and inelegant when used a lot so I mostly curtailed that. Using the term MacPort would make the term clear, but is that really a valid term in current usage? It seems we're only comfortable with the plural form, and I think that is why we always fall back to the more generic port to express a single MacPorts port. Just like Apple doesn't want you to say I wrote an AppleScript (they want you to say I wrote an AppleScript script), I don't like hearing I installed a MacPort (I think I installed a MacPorts port is clearer). That's not to say I don't see your point too. MacPorts port (and AppleScript script) is long and sounds silly. Would be neat if we could come up with a new cute term for our ports. Ruby has gems, for instance. What entities could MacPorts have? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Output of port info --depends_xyz inconsistent (usually commas but not always)
Hello all -- I have been working on a script (written in Ruby) that takes the output of the port command-line program (as suggested by Rainer recently), and parses the output looking for either port dependencies or file dependencies (note: up until yesterday, file dependences were referred to ambiguously as non-ports). I notice that in almost all cases (among a collection of 450 MacPorts I use which of course is just a fragment of what's available), that the port dependencies are separated with commas, like this: $ port info --depends_lib gnome-vfs depends_lib: port:gconf, port:dbus, port:openssl, port:libidl, port:dbus-glib, port:libxml2, port:libiconv, port:gettext But in what appears to be a minority of cases, the comma has been forgone like this: $ port info --depends_run gnome-vfs depends_run: port:desktop-file-utils port:gnome-mime-data port:shared-mime-info It was not difficult to adjust my Ruby parser to handle spaces instead of commas, but I'm wondering if it matters in terms of the strictness / policy as to how Portfiles should be authored and maintained? Thanks, T.M. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Is MacPort a valid term?
For a long time, I thought that when people were saying port, in this discussion, I thought the were referring to a port or a tcp/ip address. like localhost:80 Clarity is one of the reasons that in the past I frequently used the term MacPorts port (to distinguish it from FreeBSD and other port systems), but this is too cumbersome and inelegant when used a lot so I mostly curtailed that. Using the term MacPort would make the term clear, but is that really a valid term in current usage? It seems we're only comfortable with the plural form, and I think that is why we always fall back to the more generic port to express a single MacPorts port. Just like Apple doesn't want you to say I wrote an AppleScript (they want you to say I wrote an AppleScript script), I don't like hearing I installed a MacPort (I think I installed a MacPorts port is clearer). That's not to say I don't see your point too. MacPorts port (and AppleScript script) is long and sounds silly. Would be neat if we could come up with a new cute term for our ports. Ruby has gems, for instance. What entities could MacPorts have? Hmn. How about mport as shorthand for MacPorts port. MacPorts mport would never be used, since it is redundant. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
